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.

Sign up for GitHub

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

Jump to bottom

Switch to use Postgres as primary backend #28

Closed
dankolbman opened this issue Jan 16, 2018 · 1 comment
Closed

Switch to use Postgres as primary backend #28

dankolbman opened this issue Jan 16, 2018 · 1 comment
Labels
feature New functionality
Milestone
CHOP Sprint 1

Comments

@dankolbman
Copy link
Contributor

Although SQLite reduces dependency requirements for development, we'll need to move to Postgres for our deployments. We should at least support this in the ProductionConfig SQLALCHEMY_DATABASE_URI.
@dankolbman dankolbman added the feature New functionality label Jan 16, 2018
@baileyckelly baileyckelly added this to the CHOP Sprint 1 milestone Jan 26, 2018
@baileyckelly
Copy link
Contributor

We will need to have PG up and running for OICR by the end of this sprint.

@dankolbman dankolbman mentioned this issue Jan 30, 2018
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New functionality
Projects
None yet
Milestone
CHOP Sprint 1
Development

No branches or pull requests
2 participants
@dankolbman @baileyckelly