bida/Mastodon-documentation
5
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Include explicit production environment (#172)

Browse source 
These tasks sometimes fail under non-Docker installations when the administrator tries to run them without explicitly requesting the production environment.
This commit is contained in:
Noëlle Anthony 2017-05-01 10:32:47 -04:00 committed by wxcafé
parent dd196ab2ee
commit befab7b7c3
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Running-Mastodon/Maintenance-Tasks.md
View file

@ -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.