Skip to content
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

Upgrade to version 4.0.2 #345

Merged
merged 5 commits into from
Nov 25, 2022
Merged

Upgrade to version 4.0.2 #345

merged 5 commits into from
Nov 25, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 15, 2022

Upgrade to v4.0.2

close #344

@yunohost-bot
Copy link
Contributor

🚀
Test Badge

@Clusters Clusters mentioned this pull request Nov 15, 2022
@Clusters Clusters mentioned this pull request Nov 16, 2022
2 tasks
Fixed install issue (#344/#345) by applying the fix mentioned in this issue: mastodon/mastodon#18813.
Tested on local machine, install now seems to work. Please review/test.
@memo-567
Copy link

@yalh76

Upgrade to v4.02 and a fresh installation, both with added fix #348 by @panomaki, works to me:

Install 4.0.2~ynh1 on YunoHost 11.1.0.2 (testing). ✅
Upgrade 3.5.3~ynh4 to 4.0.2~ynh1 on YunoHost 11.1.0.2 (testing). ✅

@tituspijean
Copy link
Member

!testme

@yunohost-bot
Copy link
Contributor

yunohost-bot commented Nov 22, 2022

May the CI gods be with you!
Test Badge

@Clusters
Copy link

Clusters commented Nov 22, 2022

@tituspijean why is test job #4331 showed here? #4330 seems to be the correct one.

@tituspijean
Copy link
Member

tituspijean commented Nov 22, 2022

It looks like this is a CI bug. Someone has restarted the job, hopefully it will get it right now.


Edit: Indeed the job was duplicated, I have stopped 4331 and replaced the links with 4330 above.

@memo-567
Copy link

@yalh76

Two ideas / wishes for the upgrade script:

  1. Since the content of Mastodon is very dynamic, lots of public posts, but also possibly DM and follow-up requests in just a minute, it might be useful during an upgrade to stop the Mastodon service first and then start the backup afterwards.

Then start the service after Mastodon has been successfully updated, or the backup has been restored as usual.

That way, if something went wrong during the upgrade process, no messages will be lost.

  1. All manually .env.production changes (S3 file storage, translation options etc.) are gone and need to be re-added after an upgrade.

Can this be changed?

@panomaki
Copy link
Contributor

@memo-567 I think it would be better if you would make two issues for your requests. That way pull requests can be created addressing them. In this thread your wishes will be lost I fear...

@neosam
Copy link

neosam commented Nov 24, 2022

Is it possible to update from a different repository or branch? So I could have my own fork with custom modifications and use it for my server?

@Clusters
Copy link

@neosam this question has no relation to this PR.
Continue reading (on your own risk) here https://yunohost.org/de/packaging_apps?q=%2Fpackaging_apps#test-it as stated in the Readme file.

Can someone merge this, so no further unrelated questions may arise 😅

@neosam
Copy link

neosam commented Nov 24, 2022

Thank you. And yes, you're right, sorry. One reason I asked was that I wanted to test this PR. It's still the wrong place to ask this question, though. Apologies.

@tituspijean tituspijean merged commit d7f7299 into testing Nov 25, 2022
@tituspijean tituspijean deleted the ci-auto-update-v4.0.2 branch November 25, 2022 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants