1
Some variables from .env file being ignored i.e. ROCKET_PORT
Source: dani-garcia/vaultwarden#4497 · opened by @RT-Tap
<!-- # NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * * # --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> Subject of the issue <!-- Describe your issue here. --> ROCKET_PORT inside .env file is ignored possibly others - [i know there was an announcement about getting rid of websockets]( but I did notice that the default variable mentioned in the .env.template file ENABLE_WEBSOCKET=true does not work but WEBSOCKET_ENABLE=true does work. Because it's depreciated it shouldnt matter but I figured I would mention it as well. Others…
No pledges yet. Be the first to back this.
Comments
Similar requests
feat: allow sensitive environment variables to be the path to a file that contains the value
1 vote · 0 comments
Possibility to update PUSH_INSTALLATION_* variables in the admin panel
2 votes · 0 comments
admin UI app on different port?
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.