Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a way to recieve a token at runtime rather than hardcoded #36

Open
toastal opened this issue Mar 31, 2023 · 2 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@toastal
Copy link

toastal commented Mar 31, 2023

I keep my configs public and with gobs of services I've used, this is the first that seems to only allow hardcoded values in its file. Either allowing to be read from a file, an environment variable (could be used with systemd), or UNIX command would help clear this up.

@blinkingtwelve
Copy link

Here's a tip, since prosody-filer is in maintenance mode.

You could consider the following:

  • create a config with a bogus token (say "secretsquirrel")
  • make that public as you wish
  • using an ExecStartPre in your systemd .service file you can then patch in your actual token from your beloved environment variable using sed (or use something better, eg an actual templating language) and output it to the config file that's actually sourced (and which you won't check in) by prosody-filer.

@ThomasLeister ThomasLeister added the enhancement New feature or request label Feb 17, 2024
@ThomasLeister
Copy link
Owner

Hi! I will look into this. Config values should be set via the config file (and should be adjustable via ENV vars). 👍

@ThomasLeister ThomasLeister self-assigned this Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants