97
edits
Update Zulip Server version: Difference between revisions
Jump to navigation
Jump to search
→Upgrade Procedure
No edit summary |
|||
| Line 20: | Line 20: | ||
== Upgrade Procedure == | == Upgrade Procedure == | ||
'''Important Notes''' | '''Important Notes''' | ||
This procedure is taken from the official doc, if official doc has been updated this checklist should be updated to | This procedure is taken from the official doc, if official doc has been updated this checklist should be updated too | ||
'''Note on error emails during upgrade:''' Background workers from previous deployments may still be running when the upgrade restarts PostgreSQL. These workers will lose their database connection and crash, triggering error alert emails. This is expected behaviour and not a sign of anything wrong. One way to avoid this is to explicitly stop all Zulip services before running the upgrade script. | |||
# Fetch the latest build <code>curl -fLO https://download.zulip.com/server/zulip-server-latest.tar.gz</code> | # Fetch the latest build <code>curl -fLO https://download.zulip.com/server/zulip-server-latest.tar.gz</code> | ||
# Run the upgrade <code>/home/zulip/deployments/current/scripts/upgrade-zulip zulip-server-latest.tar.gz</code> | # Run the upgrade <code>/home/zulip/deployments/current/scripts/upgrade-zulip zulip-server-latest.tar.gz</code> | ||