Commit 8c05e867edbbfe64544021dc2ba5d777f719c4aa

Authored by Stephen Crosby
2 parents dafba351 da21fa61
Exists in master

Merge pull request #1064 from stephancom/patch-1

incorrect namespace for rake task in docs
docs/deployment/capistrano.md
... ... @@ -75,7 +75,7 @@ rbenv=1 bundle exec cap production deploy
75 75  
76 76 ## Schedule recurring tasks
77 77 You may want to periodically clear resolved errors to free up space.
78   -Schedule ```rake errbit:db:clear_resolved``` to run every day or so.
  78 +Schedule ```rake errbit:clear_resolved``` to run every day or so.
79 79  
80 80  
81 81 ## Monit
... ...
docs/deployment/heroku.md
... ... @@ -58,7 +58,7 @@ Option 1. With the heroku-scheduler add-on (replacement for cron):
58 58 heroku addons:create scheduler:standard
59 59  
60 60 # Go open the dashboard to schedule the job. You should use
61   -# 'rake errbit:db:clear_resolved' as the task command, and schedule it
  61 +# 'rake errbit:clear_resolved' as the task command, and schedule it
62 62 # at whatever frequency you like (once/day should work great).
63 63 heroku addons:create scheduler
64 64 ```
... ... @@ -73,5 +73,5 @@ heroku addons:create cron:daily
73 73 Option 3. Clear resolved errors manually:
74 74  
75 75 ```bash
76   -heroku run rake errbit:db:clear_resolved
  76 +heroku run rake errbit:clear_resolved
77 77 ```
... ...
lib/tasks/heroku/cron.rake
1 1 desc "This task is called by the Heroku cron add-on"
2 2 task cron: :environment do
3   - Rake::Task["errbit:db:clear_resolved"].invoke
  3 + Rake::Task["errbit:clear_resolved"].invoke
4 4 end
... ...