[GH-ISSUE #3] heroku deployment documentation #1

Closed
opened 2026-02-25 23:40:43 +03:00 by kerem · 5 comments
Owner

Originally created by @diwu1989 on GitHub (Oct 22, 2015).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/3

can you make it possible to deploy this on heroku easily?

Originally created by @diwu1989 on GitHub (Oct 22, 2015). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/3 can you make it possible to deploy this on heroku easily?
kerem closed this issue 2026-02-25 23:40:43 +03:00
Author
Owner

@diwu1989 commented on GitHub (Oct 30, 2015):

I forked this app and made some changes to the settings file to make it Heroku friendly
https://github.com/BetterWorks/healthchecks

<!-- gh-comment-id:152442969 --> @diwu1989 commented on GitHub (Oct 30, 2015): I forked this app and made some changes to the settings file to make it Heroku friendly https://github.com/BetterWorks/healthchecks
Author
Owner

@cuu508 commented on GitHub (Oct 30, 2015):

Thanks for heads up! I'll see if I can appropriate some of the changes you've done.
One suggestion: you can create a file local_settings.py next to settings.py and put deployment-specific settings in there. Things like Postmark configuration, NewRelic configuration, the code which looks at environment variables and so on.

<!-- gh-comment-id:152515138 --> @cuu508 commented on GitHub (Oct 30, 2015): Thanks for heads up! I'll see if I can appropriate some of the changes you've done. One suggestion: you can create a file local_settings.py next to settings.py and put deployment-specific settings in there. Things like Postmark configuration, NewRelic configuration, the code which looks at environment variables and so on.
Author
Owner

@diwu1989 commented on GitHub (Oct 31, 2015):

Deal, that's a good idea, then I'd have less merge conflicts against your version of the settings file when I merge

<!-- gh-comment-id:152697986 --> @diwu1989 commented on GitHub (Oct 31, 2015): Deal, that's a good idea, then I'd have less merge conflicts against your version of the settings file when I merge
Author
Owner

@diwu1989 commented on GitHub (Oct 31, 2015):

and 👍 for the additional 'pause' state, the try-except around the sendalerts task is the first thing I had to implement

<!-- gh-comment-id:152698542 --> @diwu1989 commented on GitHub (Oct 31, 2015): and :+1: for the additional 'pause' state, the try-except around the sendalerts task is the first thing I had to implement
Author
Owner

@diwu1989 commented on GitHub (Dec 19, 2015):

closing this issue, if anyone is interested to see how I run this on Heroku, check out my fork

<!-- gh-comment-id:165961662 --> @diwu1989 commented on GitHub (Dec 19, 2015): closing this issue, if anyone is interested to see how I run this on Heroku, check out my fork
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#1
No description provided.