Hometown v1.0.5 (Mastodon 3.4.0)

Whereas the last Mastodon update took me many months to make happen, this one I managed within 24 hours. Phew. Enjoy the latest changes from Mastodon 3.4.0. (I am still working on the next Hometown release in terms of new features.)

Changes this release:

• updating to Mastodon 3.4.0

This release is up to date with Mastodon v3.4.0, so please check there for individual patch notes if you're upgrading from a lower Mastodon version. If you're installing Hometown for the first time, please follow the instructions on the wiki.

Upgrading from v1.0.5+3.3.0

If you already have Hometown installed and are upgrading from v1.05+3.3.0, do the following:

git remote update && git checkout v1.0.5+3.4.0

As always, make sure you have backups of the database before performing any upgrades. If you are using docker-compose, this is how a backup command might look: docker exec mastodon_db_1 pg_dump -Fc -U postgres postgres > name_of_the_backup.dump

Non-Docker only:

• Install dependencies: bundle install and yarn install

Both Docker and non-Docker:

1. Run the pre-deployment database migrations by specifying the SKIP_POST_DEPLOYMENT_MIGRATIONS=true environment variable:

   • Non-Docker: SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate
   • Docker: docker-compose run --rm -e SKIP_POST_DEPLOYMENT_MIGRATIONS=true web rails db:migrate

2. Precompile the assets:

   • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
   • Docker: The assets are already precompiled during the build step

3. Restart all Mastodon processes

4. Clear cache:

   • Non-Docker: RAILS_ENV=production bin/tootctl cache clear
   • Docker: docker-compose run --rm web bin/tootctl cache clear

5. Now that the new code is running, we can finish the database migrations. This will run the post-deployment ones:

   • Non-Docker: RAILS_ENV=production bundle exec rails db:migrate
   • Docker: docker-compose run --rm web rails db:migrate

6. Restart all Mastodon processes