From befab7b7c31d1eafba896c4b97fad0bc05758b44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?No=C3=ABlle=20Anthony?= Date: Mon, 1 May 2017 10:32:47 -0400 Subject: [PATCH] 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. --- Running-Mastodon/Maintenance-Tasks.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Running-Mastodon/Maintenance-Tasks.md b/Running-Mastodon/Maintenance-Tasks.md index 03503895..2b7f4012 100644 --- a/Running-Mastodon/Maintenance-Tasks.md +++ b/Running-Mastodon/Maintenance-Tasks.md @@ -7,3 +7,5 @@ These tasks are available to instance operators: - `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.