-
Notifications
You must be signed in to change notification settings - Fork 36
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 takes forever #424
Comments
Mastodon is disk space intensive. There are currently two bottlenecks you may run into:
For now, to keep down the time you could run clean up tasks and minimize the number of days your cache keeps. See https://codeberg.org/Fedimins/mastodon-maintenance-tasks for some inspiration. |
why does the upgrade script reset file permissions ? it's why it takes all that time even without backup ... |
Where did you see that? if you’re talking about this, it’s not what you think: # Cleaning legacy permissions
if ynh_legacy_permissions_exists; then
ynh_legacy_permissions_delete_all
ynh_app_setting_delete --app=$app --key=is_public
fi
# Create a permission if needed
if ! ynh_permission_exists —-permission="api"; then
ynh_permission_create —-permission="api" --url="/api" —-allowed="visitors" —-auth_header="false" —-show_tile="false" —-protected="true"
fi |
Lines 194 to 195 in 36c4f11
Not sure those lines are required. |
Describe the bug
Upgrade is on hour 20 and is still not done.
Context
Steps to reproduce
Click upgrade and wait until the end of time.
Expected behavior
Not to take 20 hours+ to upgrade
Logs
So we are still waiting for the upgrade to complete. My question of sorts is if there is a way to trim down the backup process. Mine is 112.3 GB and if you have more than that, God help you. Maybe just back up the basic user account information (username, password, bio info) and the server info. Not all the threads, media and such.
Thanks for all your hard work!
The text was updated successfully, but these errors were encountered: