Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

poor information how to upgrade ruby to 2.7.2 #15457

Closed
jakesullyneytiri opened this issue Dec 28, 2020 · 3 comments
Closed

poor information how to upgrade ruby to 2.7.2 #15457

jakesullyneytiri opened this issue Dec 28, 2020 · 3 comments

Comments

@jakesullyneytiri
Copy link

I saw you guys released v3.3.0 but release log is way to poor when it comes to how to upgrade ruby to 2.7.2.

So i would recommend you guys to add short and best way to upgrade it correctly, if it has to be done via root or mastodon user.

Anyway i have found this https://gorails.com/setup/ubuntu/18.04 but confused if i have to do it through mastodon user or root?

So i would like a proper answer to this so it get's upgraded properly and not incorrectly.

@jakesullyneytiri
Copy link
Author

Update: Found out i only needed to run git -C /home/mastodon/.rbenv/plugins/ruby-build pull and then rvbenv install 2.7.2 to install ruby 2.7.2 and it needed to be done through mastodon user.

this might be good to add to release notes under upgrade part for 3.3.0 so users will know what to do if they are beginners.

@ariasuni
Copy link
Contributor

ariasuni commented Jan 5, 2021

I suppose a link to “Installing Ruby versions” in the release notes would be appropriate. The documentation on upgrading already says to switch to user mastodon to execute release-specific upgrade instructions, though.

@bravok
Copy link

bravok commented Nov 15, 2022

This burned me too, during the Mastodon 4.0.1 upgrade off the Digital Ocean droplet.

@vmstan vmstan converted this issue into discussion #27930 Nov 17, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants