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

Migrate data to database #16

Open
emily-noble opened this issue Apr 20, 2019 · 2 comments
Open

Migrate data to database #16

emily-noble opened this issue Apr 20, 2019 · 2 comments
Assignees

Comments

@emily-noble
Copy link
Owner

emily-noble commented Apr 20, 2019

Actual flag information should be stored in a database, making it easier to add and edit flags.

@emily-noble
Copy link
Owner Author

Looks like mysql is free on our host.

Django could support a dumpdata -> commit to repository -> flush on server -> loaddata on server workflow

@emily-noble emily-noble self-assigned this Nov 21, 2021
@emily-noble
Copy link
Owner Author

emily-noble commented Nov 21, 2021

I think the way that I'd like to handle this is to run off a sqlite database committed to the repository, even though this isn't a best practice. Given that Django has a built-in admin site that would require us exposing the admin password to the repository, this shouldn't be handled through Django's models. Instead, we want to query sqlite directly.

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

No branches or pull requests

1 participant