Mastodon 4.3 upgrade advice

sean

querkmachine sorry to have kept you waiting so long on this!

The steps to upgrade to 4.3 are as follows (replace NAME_OF_APP with your app name):

Export your Mastodon database for a backup: https://docs.opalstack.com/user-guide/postgresql-databases/#exporting-postgresql-databases

cp -r ~/apps/NAME_OF_APP ~/NAME_OF_APP.backup

Run the following commands to upgrade to 4.3.0:

cd ~/apps/NAME_OF_APP
source setenv
corepack enable --install-directory=$PWD/node/bin
yarn set version classic
cd mastodon
git fetch && git checkout v4.3.0
corepack prepare
bundle install
yarn install --immutable
RAILS_ENV=production bin/rails db:encryption:init | grep ACTIVE_RECORD_ENCRYPTION >> .env.production
RAILS_ENV=production bundle exec rails assets:precompile
SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate
../restart
RAILS_ENV=production bundle exec rails db:migrate

Your app will then be running on the 4.3.0 branch. At that point I recommend that you immediately upgrade to the latest 4.4.x branch by following the instructions at: mastodon 4.4.1

Hope this helps! Sorry once again for the delayed reply.

querkmachine

sean Thanks! I finally got around to doing it and it mostly* went off without a hitch.

I've hit on other issues with trying to get to 4.4—bundler won't work because it's the wrong version, and I can't update it because the version of Ruby is too old, it seems?—but I'm happy to sit on 4.3 for the time being.

*It took me far too long to realise that the database migration wasn't working because I'd changed the database user's password right at the start of the process. 🤦

sean

querkmachine I've hit on other issues with trying to get to 4.4—bundler won't work because it's the wrong version, and I can't update it because the version of Ruby is too old, it seems?—but I'm happy to sit on 4.3 for the time being.

The Ruby 3.2 version should be sufficient. The steps at mastodon 4.4.1 include a command to install the correct version of bundler, under the sentence "Next, update your instance to 4.4.0 with the following commands".

querkmachine

sean Yeah, that's where I encountered problems.

Trying to run the first bundle install gave me an error that it couldn't proceed because the Gemlock file expected a newer version of bundler, and in turn recommended running gem install bundler -v '~> 2.6' before bundle install.

Trying to do that returned a different error saying that it couldn't install that bundler version because the Ruby version was too old—even though I'd previously ran source scl_source enable devtoolset-11 ruby32 nodejs20, which ought to have updated it, I figure?

nick

querkmachine Did you verify the Ruby version in that session after using SCL? Try the steps again and feel free to post the output for review.

querkmachine

nick

I get to the bundle install step and it tends to go like this:

[user@server mastodon]$ bundle install
Activating bundler (~> 2.6) failed:
Could not find 'bundler' (2.6.9) required by your /home/user/apps/my_social/mastodon/Gemfile.lock.
To update to the latest version installed on your system, run `bundle update --bundler`.
To install the missing version, run `gem install bundler:2.6.9`
Checked in 'GEM_PATH=/home/user/apps/my_social/mastodon/vendor/bundle/ruby/gems:/home/user/apps/my_social/mastodon', execute `gem env` for more information

To install the version of bundler this project requires, run `gem install bundler -v '~> 2.6'`

[user@server mastodon]$ bundle update --bundler
Activating bundler (~> 2.6) failed:
Could not find 'bundler' (~> 2.6) - did find: [bundler-1.17.2]
Checked in 'GEM_PATH=/home/user/apps/my_social/mastodon/vendor/bundle/ruby/gems:/home/user/apps/my_social/mastodon', execute `gem env` for more information

To install the version of bundler this project requires, run `gem install bundler -v '~> 2.6'`

[user@server mastodon]$ gem install bundler:2.6.9
Fetching bundler-2.6.9.gem
ERROR:  Error installing bundler:
	There are no versions of bundler (= 2.6.9) compatible with your Ruby & RubyGems
	bundler requires Ruby version >= 3.1.0. The current ruby version is 2.6.5.114.

[user@server mastodon]$ source scl_source enable ruby32
[user@server mastodon]$ ruby -v
ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]

sean

querkmachine there is some kind of weird interaction if you run both source setenv and source scl_source enable ruby32 in the same shell session. If you do, it sets the shell back to the the system Ruby 2.6. The same thing happens if you run source setenv more than once in the same shell session.

If you follow the instructions exactly as presented then the upgrade to 4.3 should work as described above.

querkmachine

sean Yeah, I managed to suss that bit out ultimately. Unfortunately I encountered a different issue running bundle install failing, which I posted on the thread with the upgrade instructions.

sean

querkmachine the other thread is for upgrading to 4.4, this thread is for 4.3. Have you successfully upgraded to 4.3?

querkmachine

sean Yeah, it’s in 4.3 now

sean

Awesome, ok I'll follow up on the other thread as soon as possible.