No description
Find a file
2025-03-18 11:46:58 +01:00
.woodpecker [tests,dependencies] install and configure coverage reports 2025-03-18 00:15:33 +01:00
collector [test codestyle] shorten variable name for intentional similarity 2025-03-17 18:34:43 +01:00
config [project meta,pdm] move version information to config package 2025-03-18 11:35:16 +01:00
docs [flair] generate badges from pytest and coverage reports 2025-03-18 00:18:31 +01:00
requirements [dependencies] add pymarkdownlnt to lint markdown files 2025-03-18 11:45:42 +01:00
.env.ci [CI] Turn debug OFF on ci 2025-03-14 22:36:19 +01:00
.env.test [project] settings.py react to the DEPLOYMENT variable 2025-03-14 12:43:38 +01:00
.envrc.sample [direnv] provide sample envrc 2025-03-12 17:24:29 +01:00
.gitignore [git] add datadump to project-specific gitignore 2025-03-14 12:05:12 +01:00
justfile [just] explain - in woodpecker recipe 2025-03-18 11:46:15 +01:00
manage.py [project] start project 2025-03-12 17:23:58 +01:00
pyproject.toml [project meta,pdm] move version information to config package 2025-03-18 11:35:16 +01:00
README.md [readme] some more structure in README file 2025-03-18 11:46:58 +01:00

Teilchensammler: Collect parts in a list

Badges

status-badge Tested with Hypothesis Tests Status Coverage Status

Development

This project makes use of several tools:

  • direnv is used to set up environment variables and activate the virtualenv. I recommend installing it and integrate it into your favourite shell.
  • just is used as a task runner.
  • woodpecker-cli is used to lint .woodpecker/workflow.yaml. It is available from homebrew.
  • pytest is the test runner. Invoke it using just test (any arguments will be passed through to pytest). Several pytest-plugins are used:

Getting started

Python

Have Python >= 3.12 installed. I recommend pyenv (which in turn is easily installed by homebrew).

PostgreSQL

Set up PostgreSQL, a role and a schema. I have it on localhost, using the project name for role and schema name, and password. See .env.test for providing connection information.

Get the code

Clone the repo. cd into the project directory. (direnv should activate the virtualenv.) Run python -m pip install -U pip to upgrade pip. Then python -m pip install -r requirements/dev.txt.

Launch the dev server: just serve (or python -m django runserver when you don't have just).

Making changes

Change code, settings, templates, dependencies as you see fit. Run just lint repeatedly. Don't forget migrations. Commit often.

Using the App

just serve and open localhost:8000/collector in your browser.

Dependency management

This project uses pip-compile-multi for hard-pinning dependencies versions. Please see its documentation for usage instructions. In short, requirements/base.in contains the list of direct requirements with occasional version constraints (like Django<2) and requirements/base.txt is automatically generated from it by adding recursive tree of dependencies with fixed versions. The same goes for test and dev.

To upgrade dependency versions, run just deps (or pip-compile-multi --uv). And to install those packages run just sync. To run both of those:

just deps sync
# OR
just fd
# OR
just freshdeps

To add a new dependency without upgrade, add it to the appropriate .in file and run pip-compile-multi --no-upgrade (no just recipe yet).

Installing dependencies

For installation of dependencies always use requirement/*.txt files.

For example, the command pip install -U -r requirements/dev.txt will install testing requirements and development tools.

A useful command is pip-sync requirements/dev.txt, it uninstalls packages from your virtualenv that aren't explicitly specified as dependencies.