Marc Cataford
a341b462c7
* fix(backend): centralized settings, fix refs * build(backend): pytest configuration points at the right path * build(backend): test tooling script * ci(backend): use taskfile to trigger tests in ci * test(backend): stub db-test * ci(backend): use Task for backend steps, remove redundant bootstrap |
||
|---|---|---|
| .. | ||
| 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.