-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
heroku - persist data #44
Comments
I didn't feel like setting postgres and wasn't sure how are application would handle the downtime. |
dyno usage hours given on an account-wide basis, allowing for 24/7 uptime if needed. Accounts have a pool of hours for free dynos. |
running so closed |
Still doesn't persist whitelist. |
would have to implement db |
Or environmental variables. On Jul 28, 2016 2:03 PM, "Jon" notifications@github.com wrote:
|
oh true, possibility |
what was the reasons this was abandoned? We could set env vars for the tokens, etc. Just have to work in postgresql instead of txt files as the read-only fs restriction.
The text was updated successfully, but these errors were encountered: