resonant-geo-cookiecutter

Develop with Docker (recommended quickstart)

This is the simplest configuration for developers to start with.

Initial Setup

1. Run docker compose run --rm django ./manage.py migrate
2. Run docker compose run --rm django ./manage.py createsuperuser and follow the prompts to create your own user

Run Application

1. Run docker compose up
2. Access the site, starting at http://localhost:8000/admin/
3. When finished, use Ctrl+C

Application Maintenance

Occasionally, new package dependencies or schema changes will necessitate maintenance. To non-destructively update your development stack at any time:

1. Run docker compose pull
2. Run docker compose build --pull --no-cache
3. Run docker compose run --rm django ./manage.py migrate

Develop Natively (advanced)

This configuration still uses Docker to run attached services in the background, but allows developers to run Python code on their native system.

Initial Setup

1. Run docker compose -f ./docker-compose.yml up -d
2. Install Python 3.13
3. Create and activate a new Python virtualenv
4. Run pip install -e .[dev]
5. Run source ./dev/export-env.sh
6. Run ./manage.py migrate
7. Run ./manage.py createsuperuser and follow the prompts to create your own user

Run Application

1. Ensure docker compose -f ./docker-compose.yml up -d is still active
2. Run:
   1. source ./dev/export-env.sh
   2. ./manage.py runserver
3. Run in a separate terminal:
   1. source ./dev/export-env.sh
   2. celery --app resonant_geo_cookiecutter.celery worker --loglevel INFO --without-heartbeat
4. When finished, run docker compose stop
5. To destroy the stack and start fresh, run docker compose down -v

Testing

Initial Setup

tox is used to execute all tests. tox is installed automatically with the dev package extra.

When running the "Develop with Docker" configuration, all tox commands must be run as docker compose run --rm django tox; extra arguments may also be appended to this form.

Running Tests

Run tox to launch the full test suite.

Individual test environments may be selectively run. This also allows additional options to be be added. Useful sub-commands include:

• tox -e lint: Run only the style checks
• tox -e type: Run only the type checks
• tox -e test: Run only the pytest-driven tests

To automatically reformat all code to comply with some (but not all) of the style checks, run tox -e format.