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.
Major changes
uv
Docker best practices (see https://docs.astral.sh/uv/guides/integration/docker/)skaffold dev
(removes the need for image build and redeployment in most scenarios)Settings
Pydantic Settings are used to control behavior of the backend (see
config.py
). The following settings are currently available:AUTO_MIGRATE: bool
controls whether Alembic migrations should be automatically applied if the database is out-of-syncDB_CONNECTION_STRING: str
sets the connection string used to connect to the databaseThese settings can be passed through environment variables of the same name.
Database Migrations
Alembic is used to perform database migrations.
As part of its entry point script, the container image automatically upgrades to the
head
revision (alembic upgrade head
).For local development, the
AUTO_MIGRATE
setting can be used to automatically run migrations on startup (or you can manually use the Alembic CLI).Tests
The automatic
db
fixture in the integration test suite provides an in-memory SQLite database session.Closes #133