You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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?
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.
The text was updated successfully, but these errors were encountered: