1
Specified environment variables into config.json
Source: dani-garcia/vaultwarden#1537 · opened by @pepa65
Instead of always giving precedence to pre-existing config.json entries, is it not a better idea to give precedence to set environment variables? And then I mean overwriting entries in the config.json whenever environment variables are specified on startup.
I already do this in a patch script myself for admin_token/ADMIN_TOKEN, when I want to specify a new one on startup. This doesn't preclude usage of the Admin page, they can be used both, and doing things this way would make more sense to me.
I already do this in a patch script myself for admin_token/ADMIN_TOKEN, when I want to specify a new one on startup. This doesn't preclude usage of the Admin page, they can be used both, and doing things this way would make more sense to me.
No pledges yet. Be the first to back this.
Comments
Similar requests
Update Podman documentation to use Quadlet for systemd deployment
5 votes · 0 comments
feat: allow sensitive environment variables to be the path to a file that contains the value
1 vote · 0 comments
Bitwarden in Disclaimer
1 vote · 0 comments
Possibility to update PUSH_INSTALLATION_* variables in the admin panel
2 votes · 0 comments
Stable customization variables for branding (logo, colors) across updates
2 votes · 0 comments
No comments yet.