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

establish a database migration strategy #318

Open
adamdecaf opened this issue Mar 26, 2018 · 1 comment
Open

establish a database migration strategy #318

adamdecaf opened this issue Mar 26, 2018 · 1 comment

Comments

@adamdecaf
Copy link
Contributor

Right now keeping a postgres database for tls-observatory is an artisanal chore. We should automate it instead so as to not create issues for users deploying their own instances.
(See #317)

Personally I've used https://github.com/rubenv/sql-migrate before, but I'm sure there are a wealth of other options. awesome-go offers a few other migration tools.

@jvehent
Copy link
Contributor

jvehent commented Mar 27, 2018

I'm ok with using a migration tool, especially if its automated (deploying the production service is fully automated so it'd be nice to not require manual commands).
If you already have experience with a specific tool, would you mind proposing a patch?

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

No branches or pull requests

2 participants