Change how we run migrations or initialize the database on a fresh installs #132
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #119
This was a much bigger change than I expected. Most of it was due to how the aws deployment works, but it should be a-okay now.
There were some issues in one of the migration scripts as well, it was trying to drop columns that didn't exist. I uh, commented out the problem parts.
On the front-end side I discovered that if we declare a route like
@get('/')
the frontend must include the slash at the end, otherwise fastapi will redirect, which causes issues to the nginx rewrite config. I couldn't find a good solution other than to just add slashes at the end of some of these calls.Changes:
BREAKING: Added
appointment
module folder insrc
.BREAKING: alembic.ini should now be placed in the backend root folder. You will need to grab a fresh copy as there's been additional changes.
Added a super simple cli interface handled by main.py
Adjusted main.py to bootstrap either a fast api server or a cli interface.
Added a
update-db
command that is installed when pip install this module.The
update-db
command will initialize a fresh database or run migrations, resolving most of our database woes.New folder structure more closely matches the deployed folder structure for easier deployments.
Local docker now only mounts the
src
folderCommented out some non-existent columns/constraints in a recent migration
Added missing trailing slash to the frontend for
schedule/
Added sentry support to migrations
Adjusted code-referenced folder locations as required