Update the readme and simplify the setup process #13

Open
opened 2024-07-28 00:15:03 +02:00 by oysteikt · 0 comments
Owner

If you follow the list of commands in the README as they are now, the setup will not work. poetry run alembic migrate is not a real command, and alembic needs the config to be inplace before you run it.

The whole setup process is a bit of a mess, so it would be nice if the command count could be kept to a minimum. Maybe remove the "run flask to set up the database as a side-effect" step, and potentially interactively ask if you should automigrate unless --no-automigrate is given. The --no-automigrate should probably be used in any potential systemd unit (see #5).

Alternatively, add a flag to opt-in to both create, automigrate and seed the database (and potentially nuke any existing database to get a fresh new start upon starting the program anew).

If you follow the list of commands in the README as they are now, the setup will not work. `poetry run alembic migrate` is not a real command, and `alembic` needs the config to be inplace **before** you run it. The whole setup process is a bit of a mess, so it would be nice if the command count could be kept to a minimum. Maybe remove the "run flask to set up the database as a side-effect" step, and potentially interactively ask if you should automigrate unless `--no-automigrate` is given. The `--no-automigrate` should probably be used in any potential systemd unit (see #5). Alternatively, add a flag to opt-in to both create, automigrate and seed the database (and potentially nuke any existing database to get a fresh new start upon starting the program anew).
oysteikt added the
bug
feature request
labels 2024-07-28 00:15:03 +02:00
oysteikt added this to the Initial release milestone 2024-07-28 00:24:25 +02:00
Sign in to join this conversation.
No description provided.