-
Notifications
You must be signed in to change notification settings - Fork 48
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
Setup database migrations #59
Comments
lock.aquire() |
@joshfraser @hucares This is now done, right? |
Yes. Issue should auto close on github when referenced by PR that’s closed
but doesn’t for some reason
…On Sat, Feb 17, 2018 at 4:24 PM Stan James ***@***.***> wrote:
@joshfraser <https://github.com/joshfraser> @hucares
<https://github.com/hucares> This is now done, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAR87MgBvBNJFvwEfzUABGGmeF3fOdqQks5tV23DgaJpZM4Ry3m0>
.
|
Sweet. Thanks for your help on that, @hucares ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like we're going to have more database stuff than we initially thought. We're going to need to set up database migrations to make it more manageable when we need to make changes to the database.
Flask-Migrate is probably the best way to go here. We just need someone to set it up.
https://flask-migrate.readthedocs.io/en/latest/
The text was updated successfully, but these errors were encountered: