From d8a9f709203501b1f920ecf9327ffbf40c4a85e4 Mon Sep 17 00:00:00 2001 From: Eugen Rochko Date: Tue, 25 Jul 2017 17:40:04 +0200 Subject: [PATCH] Update Maintenance-Tasks.md --- Running-Mastodon/Maintenance-Tasks.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/Running-Mastodon/Maintenance-Tasks.md b/Running-Mastodon/Maintenance-Tasks.md index cd76b95b..36022497 100644 --- a/Running-Mastodon/Maintenance-Tasks.md +++ b/Running-Mastodon/Maintenance-Tasks.md @@ -1,12 +1 @@ -# 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:media:remove_silenced` remove media attachments attributed to silenced accounts. -- `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. +[See list of rake tasks](List-of-Rake-tasks.md)