Closed ycecube closed 2 years ago
You should look at their Help Page for this: https://bitwarden.com/help/updating-on-premise/
Well, okay but just after that, the next paragraph says, "It is critically important to keep your self-hosted Bitwarden instance up to date." :)
Wouldn't it make more sense to use the latest tag for the docker images? So, the script wouldn't have to keep track of the version numbers.
Well, okay but just after that, the next paragraph says, "It is critically important to keep your self-hosted Bitwarden instance up to date." :)
Yes, but they want to "test" the update before it breaks something on an self-hosted instance.
Wouldn't it make more sense to use the latest tag for the docker images? So, the script wouldn't have to keep track of the version numbers.
Then you probably could receive test versions, that aren't supposed to be deployed on a live system.
Hey @ycecube, as @Jniklas2 has pointed out, our self-hosted release can be several days behind our cloud server releases. Stay tuned as we roll out these updates soon. Thanks!
I still think that it should be done the same date when your upgrade your cloud service. Self-hosted environments could be potentially open to the same dangers regardless of where it is being hosted, it is important especially with open source software.
I understand that the latest tag could be a test release, but in that case, wouldn't it make sense to add a production tag? This is how nextcloud does it for example.
Hi,
As of now the current server version is 2022.9.1 but the
bitwarden.sh
script still downloads the previous version, 8.1 for the web version and 8.4 for the server version.Can you please check?