Skip to content
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

Open
jonobrien opened this issue May 18, 2016 · 7 comments
Open

heroku - persist data #44

jonobrien opened this issue May 18, 2016 · 7 comments
Labels

Comments

@jonobrien
Copy link
Collaborator

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.

@Omodi
Copy link
Owner

Omodi commented May 18, 2016

I didn't feel like setting postgres and wasn't sure how are application would handle the downtime.

@jonobrien
Copy link
Collaborator Author

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.

@jonobrien
Copy link
Collaborator Author

running so closed

@Omodi
Copy link
Owner

Omodi commented Jul 28, 2016

Still doesn't persist whitelist.

@Omodi Omodi reopened this Jul 28, 2016
@jonobrien
Copy link
Collaborator Author

would have to implement db

@jonobrien jonobrien changed the title heroku heroku - persist data Jul 28, 2016
@Omodi
Copy link
Owner

Omodi commented Jul 28, 2016

Or environmental variables.

On Jul 28, 2016 2:03 PM, "Jon" notifications@github.com wrote:

would have to implement db


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#44 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACzDS8qfpKbVB4VEauWFP1cbZGHVdeqsks5qaO74gaJpZM4Ig7Ii
.

@jonobrien
Copy link
Collaborator Author

oh true, possibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants