zelo72
/
documentation
mirror of https://github.com/mastodon/documentation
1
0
Fork 0
Code Issues 6 Releases Wiki Activity

Remove instructions for cleanup crons (#1529) 

Since the retention policy for cached content and media was added (#19232) a external cron is no longer needed.
This commit is contained in:
Alyx 2024-10-08 15:08:38 +01:00 committed by GitHub
parent 1fc8c2a889
commit 4f83524882
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 0 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
content/en/admin/setup.md
View File

@ -47,20 +47,3 @@ After logging in, navigate to the **Site settings** page (under **Preferences**
| Custom extended information | You can put all sorts of information in here but a **code of conduct** is recommended |
After you fill these in, click “Save changes”.
## Running periodic cleanup tasks {#cleanup}
Mastodon generates some temporary files that are worth cleaning up after a certain amount of time (e.g. to save money on hosting). In general, you want to set up `cron` jobs (or another mechanism) to run these periodic cleanup tasks.
Typically you want to run [`tootctl media remove`](https://docs.joinmastodon.org/admin/tootctl/#media) and [`tootctl preview_cards remove`](https://docs.joinmastodon.org/admin/tootctl/#preview_cards) periodically. These will clean up remote media (e.g. images, videos, audio) and preview cards (e.g. preview images for links) after a certain number of days. (Check the docs for those commands if you want to tweak how old something has to be before it's cleaned up.)
First, run `crontab -e` to edit the cronfile for the `mastodon` user. (If you get a prompt asking which editor to use, choose your favorite editor.)
Next, add something like the following to the bottom of the file:
@weekly RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove
@weekly RAILS_ENV=production /home/mastodon/live/bin/tootctl preview_cards remove
This will run these two commands on a weekly basis.
Finally, save the file. You can use `crontab -l` to verify the configuration.