-
Notifications
You must be signed in to change notification settings - Fork 308
Setup a staging environment on heroku #4465
Comments
Yay! I have a basic app up: http://gratipay-staging.herokuapp.com/?tab=approved |
Heroku pipelines don't seem to support organization accounts :/ Every time I try to create one, it gets created under my person account. I tried the CLI tool too, didn't work. I've written to support asking if there is a workaround. |
This has been super useful! I've already upgraded us from cedar-14 to heroku-16, and removed one extra step from payday. |
We don't have access to free dynos though, I had to manually dial down the web dyno count to 0 once I was done. |
Hmm, the heroku postgres DB we get is always 9.6.1, not 9.6.2 (like we have on production). Looks like they have a lot of old pre-made DBs for the hobby tier that haven't exhausted? I've written to support asking for help. |
Heard back from heroku -
|
Heard back..
|
Managed to get a 9.6.2 DB attached. |
Will this staging server be long-lived? Could we get some docs on usage, maybe as a howto on Inside Gratipay? |
The app will be long-lived, but as of now I'm only activating dynos as and when we need them.
Definitely. I'm going to keep this open for a while until I manage to lower the barrier of entry - via docs, processes etc. |
While working on #4460, realized that it would be useful to have a separate app ready to test configuration changes.
The text was updated successfully, but these errors were encountered: