diff options
| author | panomaki <p45+github@freedom.nl> | 2023-04-12 11:30:43 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-12 11:30:43 +0200 |
| commit | 30f48695dae1594af4ad43a081fe5387378e70ce (patch) | |
| tree | 7d5594db31fbbd0b7aaf0822c825e6b6bccf135b /README.md | |
| parent | 21a9f171b83de4bc8cace4f41c81b28f7661deac (diff) | |
| download | mastodon_ynh-30f48695dae1594af4ad43a081fe5387378e70ce.tar.gz mastodon_ynh-30f48695dae1594af4ad43a081fe5387378e70ce.tar.bz2 mastodon_ynh-30f48695dae1594af4ad43a081fe5387378e70ce.zip | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -60,9 +60,12 @@ $ screen -r Upgrading from 3.5.3 to 4.1.2 directly has not been integration-tested. It is recommended to do a two-step upgrade: Mastodon can grow huge. You could consider cleaning up your local cache first as otherwise your backup will be very big: -'sudo cd /var/www/mastodon/live && sudo -u mastodon RAILS_ENV=production PATH=/opt/rbenv/versions/mastodon/bin bin/tootctl media remove --days=0 --dry-run' + +`$ sudo cd /var/www/mastodon/live && sudo -u mastodon RAILS_ENV=production PATH=/opt/rbenv/versions/mastodon/bin bin/tootctl media remove --days=0 --dry-run` + If all looks good commit the cleanup: -'sudo cd /var/www/mastodon/live && sudo -u mastodon RAILS_ENV=production PATH=/opt/rbenv/versions/mastodon/bin bin/tootctl media remove --days=0' + +`$ sudo cd /var/www/mastodon/live && sudo -u mastodon RAILS_ENV=production PATH=/opt/rbenv/versions/mastodon/bin bin/tootctl media remove --days=0 ` First upgrade to 4.0.2~ynh2: |
