WEBSOCKET_ENABLED was renamed to ENABLE_WEBSOCKET after v1.29.0

fenggwsx
2025-01-11 14:59:02 +08:00
parent b6cffc3545
commit 36dc049d78

@@ -13,8 +13,8 @@ If you do use a reverse proxy like nginx or Apache HTTPd, then you need to make
<br>
The old `WEBSOCKET_ENABLED` and `WEBSOCKET_PORT` are not needed anymore since v1.29.0 of Vaultwarden and can be ignored.<br>
In fact, if you use the native implementation setting `WEBSOCKET_ENABLED` back to the default `false` value will reduce resources used by Vaultwarden (though not that much).
The old `WEBSOCKET_ENABLED` and `WEBSOCKET_PORT` have been deprecated since v1.29.0 of Vaultwarden and will be ignored.<br>
After v1.29.0, you can disable Websocket notifications by setting `ENABLE_WEBSOCKET` to the `false` value, which will reduce resources used by Vaultwarden (though not that much).
<br>