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

Schema migrations desirable #41

Open
nerdstrike opened this issue Mar 30, 2022 · 1 comment
Open

Schema migrations desirable #41

nerdstrike opened this issue Mar 30, 2022 · 1 comment
Labels
enhancement New feature or request
Milestone
v1

Comments

@nerdstrike
Copy link
Contributor

A tool like Alembic can provide us with safe schema management for the dev and production databases. At the very least we need to have controlled upgrade and history of schema changes so that the two services can remain in sync.

Configure Alembic to deploy the v1 schema, and subsequently generate schema patches for future changes.
@nerdstrike nerdstrike added the enhancement New feature or request label Mar 30, 2022
@nerdstrike nerdstrike added this to the v1 milestone Mar 30, 2022
@nerdstrike
Copy link
Contributor Author

Also we need to standardise a procedure for telling users about downtime, issue the schema changes, and restore service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v1
Development

No branches or pull requests
1 participant
@nerdstrike