documentation/Running-Mastodon/Maintenance-Tasks.md

# Maintenance tasks

These tasks are available to instance operators:

- `rake mastodon:media:clear` removes uploads that have not been attached to any status after a while, you would want to run this from a periodic cronjob
- `rake mastodon:push:clear` unsubscribes from PuSH notifications for remote users that have no local followers. You may not want to actually do that, to keep a fuller footprint of the fediverse or in case your users will soon re-follow
- `rake mastodon:push:refresh` re-subscribes PuSH for expiring remote users, this should be run periodically from a cronjob and quite often as the expiration time depends on the particular hub of the remote user
- `rake mastodon:feeds:clear_all` removes all timelines, which forces them to be re-built on the fly next time a user tries to fetch their home/mentions timeline. Only for troubleshooting
- `rake mastodon:feeds:clear` removes timelines of users who haven't signed in lately, which allows to save RAM and improve message distribution. This is required to be run periodically so that when they login again the regeneration process will trigger

If you receive an error, such as `WARNING: Sidekiq testing API enabled, but this is not the test environment.  Your jobs will not go to Redis.`, try adding `RAILS_ENV=production ` to the beginning of each task.
Import from main repo README (#82) * Add docker guide from main repo readme * Add maintenance tasks doc to running section * Clean up markdown in prod guide * Move guidance to use tagged releases to docs * Move local domain and host config to docs repo * Title of page * Update Production-guide.md 2017-04-18 16:32:47 +02:00			`# Maintenance tasks`

			`These tasks are available to instance operators:`

			- `rake mastodon:media:clear` removes uploads that have not been attached to any status after a while, you would want to run this from a periodic cronjob
			- `rake mastodon:push:clear` unsubscribes from PuSH notifications for remote users that have no local followers. You may not want to actually do that, to keep a fuller footprint of the fediverse or in case your users will soon re-follow
			- `rake mastodon:push:refresh` re-subscribes PuSH for expiring remote users, this should be run periodically from a cronjob and quite often as the expiration time depends on the particular hub of the remote user
			- `rake mastodon:feeds:clear_all` removes all timelines, which forces them to be re-built on the fly next time a user tries to fetch their home/mentions timeline. Only for troubleshooting
			- `rake mastodon:feeds:clear` removes timelines of users who haven't signed in lately, which allows to save RAM and improve message distribution. This is required to be run periodically so that when they login again the regeneration process will trigger
Include explicit production environment (#172) These tasks sometimes fail under non-Docker installations when the administrator tries to run them without explicitly requesting the production environment. 2017-05-01 16:32:47 +02:00
			If you receive an error, such as `WARNING: Sidekiq testing API enabled, but this is not the test environment. Your jobs will not go to Redis.`, try adding `RAILS_ENV=production ` to the beginning of each task.