1.0 Upgrade Instructions

Preparations

• Make sure you have working backups, and test that they can be restored (e.g. to your local computer)
• Tune your database for the specific hardware to make the migrations run faster
• Before upgrading the production server, you can test if the migration works correctly and see how long it takes. For this take the backup from above and load it into a test database. Then run the latest 1.0 release with that database. If the test upgrade fails, open an issue.
• On lemmy.ml the migrations take about 24 hours, during which the site will be inaccessible. Post an announcement about the planned upgrade time and use “Feature in Local” so that all users see it.
• If you use Ansible, specify the version explicitly in hosts file, for example lemmy_version=1.0.0-beta.1.

Run the Upgrade

• If you run with multiple Lemmy backend processes as described in horizontal scaling, make sure only one is active while running migrations.
• Adjust lemmy-ui environment variables. The important ones are:

- LEMMY_UI_BACKEND_INTERNAL=http://lemmy:8536
- LEMMY_UI_BACKEND=https://voyager.lemmy.ml

• Adjust lemmy.hjson config variables.
  • Instead of separate database fields host, password etc, there is a single connection url
  • The email section also uses a connection url
• Upgrade version names in your docker-compose.yml file (eg replace dessalines/lemmy:0.19.XX with dessalines/lemmy:1.0.0-beta.1)
• Wait for migrations to complete (this may take many hours as noted above)
• Test that the site is working as expected