Zulip Maintenance: Difference between revisions
(Created page with "{{Article |MainNavigation=No }}") |
(Init) |
||
| Line 1: | Line 1: | ||
{{Article | Some rough notes on running Zulip: | ||
* it requires to run on its own VPS, eg it does not like if you setup other web services (with Nginx) on the same machine | |||
* it needs something slightly more than a basic small VPS, as it runs Python and needs enough CPU and disk space to run decently | |||
* in my experience (maybe due to having left-overs of other web services setup on the same machine, see first point), after each upgrade the HTTPS certificate would break | |||
Given this, the installation instruction are quite clear https://zulip.readthedocs.io/en/stable/production/install.html. | |||
=== Upgrading === | |||
Refer to the [https://zulip.readthedocs.io/en/stable/production/upgrade-or-modify.html#upgrading-to-a-release official docs]. We're not running Zulip inside Docker or patching Zulip, so the default instructions can be followed as-is. | |||
Steps: | |||
* SSH-login to the VPS | |||
* download the latest version of Zulip: <code>curl -fLO <nowiki>https://download.zulip.com/server/zulip-server-latest.tar.gz</nowiki></code> | |||
* run this command: <code>sudo /home/zulip/deployments/current/scripts/upgrade-zulip zulip-server-latest.tar.gz</code> | |||
* wait for the upgrade to take place and note if any errors is being reported during the process; during this time Zulip will be offline for a few minutes only (hopefully) | |||
* as I'm not sure if the HTTPS problem still happens after a Zulip upgrade, but I remove any left-over of Nginx from the system except Zulip's own files, I'll upgrade this entry after the next upgrade! | |||
Please check [https://zulip.readthedocs.io/en/stable/production/install.html#troubleshooting this Troubleshooting section] in case of problems (how to look up logs, debug, etc).{{Article | |||
|MainNavigation=No | |MainNavigation=No | ||
}} | }} | ||
[[Category:Maintenance]] | |||
Revision as of 11:28, 2 March 2023
Some rough notes on running Zulip:
- it requires to run on its own VPS, eg it does not like if you setup other web services (with Nginx) on the same machine
- it needs something slightly more than a basic small VPS, as it runs Python and needs enough CPU and disk space to run decently
- in my experience (maybe due to having left-overs of other web services setup on the same machine, see first point), after each upgrade the HTTPS certificate would break
Given this, the installation instruction are quite clear https://zulip.readthedocs.io/en/stable/production/install.html.
Upgrading
Refer to the official docs. We're not running Zulip inside Docker or patching Zulip, so the default instructions can be followed as-is.
Steps:
- SSH-login to the VPS
- download the latest version of Zulip:
curl -fLO https://download.zulip.com/server/zulip-server-latest.tar.gz - run this command:
sudo /home/zulip/deployments/current/scripts/upgrade-zulip zulip-server-latest.tar.gz - wait for the upgrade to take place and note if any errors is being reported during the process; during this time Zulip will be offline for a few minutes only (hopefully)
- as I'm not sure if the HTTPS problem still happens after a Zulip upgrade, but I remove any left-over of Nginx from the system except Zulip's own files, I'll upgrade this entry after the next upgrade!
Please check this Troubleshooting section in case of problems (how to look up logs, debug, etc).