Global.override.env changes?

Ask the Community Password Manager
1

Hi,

Since server version 1.40.0 there has been a removal of a number of settings within global.override.env for self hosted installations.

These settings are shown below however I’d like to seek clarification of whether or not they are required for versions post 1.40.0?

globalSettings__baseServiceUri__api=https://bitwarden.example.com/api
globalSettings__baseServiceUri__identity=https://bitwarden.example.com/identity
globalSettings__baseServiceUri__admin=https://bitwarden.example.com/admin
globalSettings__baseServiceUri__notifications=https://bitwarden.example.com/notifications
globalSettings__baseServiceUri__sso=https://bitwarden.example.com/sso
globalSettings__baseServiceUri__portal=https://bitwarden.example.com/portal
globalSettings__attachment__baseDirectory=/etc/bitwarden/core/attachments
globalSettings__attachment__baseUrl=https://bitwarden.example.com/attachments
globalSettings__send__baseDirectory=/etc/bitwarden/core/attachments/send
globalSettings__send__baseUrl=https://bitwarden.example.com/attachments/send
globalSettings__dataProtection__directory=/etc/bitwarden/core/aspnet-dataprotection
globalSettings__syslog__destination=
globalSettings__licenseDirectory=/etc/bitwarden/core/licenses
globalSettings__logDirectory=/etc/bitwarden/logs
globalSettings__logRollBySizeLimit=

2 Likes
2

I’m interested too

3

+1 following also

4

By “removal of a number of settings within global.override.env for self hosted installations”, do you mean removed from Bitwarden or removed from the Install and Deploy - Linux FAQ?

LogRollBySizeLimit is still an applicable setting that, as far as I can tell, is not restricted from use by self hosted.

On the other hand, there have been a lot of added GlobalSettings which, again as far as I can tell, are not restricted from use by self hosted but are not at all documented anywhere. HCaptcha settings, for example.

I agree with what I think is the substance of your post. That Bitwarden could, and should, do a much better job of documenting available settings, even if they feel they are the only ones who use some settings:

This article will not define every environment variable, instead focusing on those used or configured by most installations.

“Every environment variable” should be documented somewhere, together, for admins who diverge from the category of “most installations”.