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

Expose AWS postgres instance and update default db properties #6

Open
DanielJRutledge opened this issue May 22, 2017 · 2 comments
Open
Assignees

Comments

@DanielJRutledge
Copy link
Collaborator

Expose the EC2 Postgres instance and have the postgres properties default to that as opposed to a local instance. This way contributors don't have to have a db dump to contribute anything to server-side development.

@DanielJRutledge DanielJRutledge changed the title Expose AWS postgres instance and default db properties Expose AWS postgres instance and update default db properties May 22, 2017
@DanielJRutledge
Copy link
Collaborator Author

DanielJRutledge commented May 22, 2017

Thought: we will probably have to tweak the postgres user again to read-only if we publish the authentication credentials.

@emptyflash
Copy link
Collaborator

emptyflash commented May 22, 2017

I agree with this, especially because we're not doing anything on the frontend or api to change the database as of right now. In the far future, when we're potentially authenticating with overdrive and storing user data, it'd probably be best to have a dev and stage environment for that kind of thing and/or make it trivial to set up and populate local dbs.

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

No branches or pull requests

2 participants