2
Possibility to update PUSH_INSTALLATION_* variables in the admin panel
Source: dani-garcia/vaultwarden#4164 · opened by @Getslow6
Hi,
Maybe this has been requested before already, but couldn't find it.
As a Home Assistant user, I'm running the Vaultwarden container as an addon to Home Assistant. In the Home Assistant Operating System we don't have direct access to the environment variables, as the Vaultwarden container is 'wrapped' to become the Home Assistant addon.
In order to enable the push notification service, we need to be able to set the following environment variables:
Two feature requests have been opened in he [Vaultwarden Addon]( project:
• • The maintainer mentioned that this should preferably be added upstream - here - which makes sense in my opinion.
Would it be possible to make the environment variables adaptable from the Admin page?
Maybe this has been requested before already, but couldn't find it.
As a Home Assistant user, I'm running the Vaultwarden container as an addon to Home Assistant. In the Home Assistant Operating System we don't have direct access to the environment variables, as the Vaultwarden container is 'wrapped' to become the Home Assistant addon.
In order to enable the push notification service, we need to be able to set the following environment variables:
Two feature requests have been opened in he [Vaultwarden Addon]( project:
• • The maintainer mentioned that this should preferably be added upstream - here - which makes sense in my opinion.
Would it be possible to make the environment variables adaptable from the Admin page?
No pledges yet. Be the first to back this.
Comments
Similar requests
Move SSO_CLIENT_SECRET to the Read Only Admin Panel or Encrypt it
1 vote · 0 comments
feat: allow sensitive environment variables to be the path to a file that contains the value
1 vote · 0 comments
Set different entries for the Admin panel
1 vote · 0 comments
Stable customization variables for branding (logo, colors) across updates
2 votes · 0 comments
Specified environment variables into config.json
1 vote · 0 comments
No comments yet.