Marc Cataford
ee9a9d8dc3
* build(backend): more verbosity on test + error handling * fix(backend): raise HTTPException, not return on details fetch * fix(backend): get inserted ID instead of row tuple * test(backend): add tests for list + details routes |
||
|---|---|---|
| .. | ||
| rotini | ||
| script | ||
| tests | ||
| .pylintrc | ||
| .python-version | ||
| docker-compose.yml | ||
| pyproject.toml | ||
| README.md | ||
| requirements.in | ||
| requirements.txt | ||
| requirements_dev.in | ||
| requirements_dev.txt | ||
Rotini backend
Development
Before starting, make sure to run the root bootstrap script so the task commands are enabled.
Locally, a Postgres database that can be used for development can be started via docker-compose up -d.
An envfile should be present at .env and should define:
DATABASE_USERNAME, the username to initialize the DB user with;DATABASE_PASSWORD, the password to assign to that test user;DATABASE_HOST, the host on which the database runs;DATABASE_PORT, the port on which the database runs;DATABASE_NAME, name of the database within the Postgres instance.