abby/abhilasha
1
0
Fork 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions

TODO: Database Migration #4

New issue
Closed
opened 2026-03-21 04:47:09 +00:00 by abhifig · 0 comments
abhifig commented 2026-03-21 04:47:09 +00:00 (Migrated from codeberg.org)
Copy link

Add scripts to create performances table and populate with sample data depending on whether building the project for development or production.

Things to research/investigate:

  • Does it make sense to use scripts for sample data to store/version control the list of gigs? This way each build on the eventual server could trigger a docker compose down -v to purge the database and rebuild it fresh with all performances each time. (This probably makes no sense for any REAL project besides this ...)
  • How should the data be backed up? A simple (and version-controllable) way that I'm sure is wrong for production would be to maintain a CSV file which can always easily be added to the DB via dbeaver.
Add scripts to create performances table and populate with sample data depending on whether building the project for development or production. Things to research/investigate: - Does it make sense to use scripts for sample data to store/version control the list of gigs? This way each build on the eventual server could trigger a `docker compose down -v` to purge the database and rebuild it fresh with all performances each time. (This probably makes no sense for any REAL project besides this ...) - How should the data be backed up? A simple (and version-controllable) way that I'm sure is wrong for production would be to maintain a CSV file which can always easily be added to the DB via dbeaver.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
woodpecker-ci-workflow-testing
workflow
database-migration
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
abby/abhilasha#4
No description provided.