FLUXER_NATS_AUTH_TOKEN is only read and used(?) by gateway

(#803) Bug Fixed self-hosting

1mo agoby RexSystem originally by @MrRubberDucky on GitHub

Thread

RexSystem 1 vote 28d ago originally by @MrRubberDucky on GitHub OP

Hmm I can see that docs has an entry for it https://docs.fluxer.app/operator/configuration/#fluxer_nats_auth_token Is it only used for api, gateway and worker specific authorization? Tried implementing following into my nats.conf after I had written this issue

listen: "0.0.0.0:4222"
authorization {
    token: "meow-meow" <- https://docs.nats.io/learn/security/authentication-basics#other-ways-a-user-entry-can-authenticate
}
jetstream {
    store_dir: "/data"
    max_memory_store: 4GB
    max_file_store: 40GB
}

Simply adding this environment variable without modifying NATS config does not really seem to do much either, no clear indication it's used anywhere. Mostly just adding extra noise to the pile with my findings.

Permalink