Skip to content

Commit 395f5f5

Browse files
author
Austin Schneider
committed
updated docs
1 parent 0f8c1bf commit 395f5f5

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

README.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,26 @@ Pinger is a good open source alternative for website monitoring. Set up an alert
1010

1111
## Running on Heroku
1212

13+
These instructions assume you have a good understanding of Heroku.
14+
1315
* Create an app on Heroku on the cedar stack
1416
* Setup Redis
1517
* Add the Redis To Go add-on
1618
* In the config directory, copy `redis_config.yml.example` to `redis_config.yml`
1719
* Fill in the values provided by the add-on
1820
* Setup Resque
1921
* In the config directory, copy `resque_config.yml.example` to `resque_config.yml`
20-
* The `web_user` and `web_pass` is the login credentials for viewing your queues at the http://yourapp.herokuapp.com/resque
22+
* The `web_user` and `web_pass` are the login credentials for viewing your queues at the yourapp.herokuapp.com/resque
23+
* Deploy to Heroku
24+
25+
Running this application requires 3 running processes: a web server, worker, and scheduler. This can get quite expensive on Heroku, as they charge $0.05/hour per process. To run this app for free, try this:
26+
27+
* Create 3 Heroku apps, one for each process. For example: pinger-web, pinger-worker and pinger-scheduler
28+
* Only install the Redis To Go add-on on the worker app
29+
* Make sure all 3 apps have the same DATABASE_URL environment variable
30+
* Make sure the web app runs the web process only, the worker app runs the worker process only and the scheduler app runs the scheduler process only
31+
32+
If you're having troubles or find a bug with these instruction, please add a github issue.
2133

2234
## Technologies
2335

0 commit comments

Comments
 (0)