Snapshot: alpha-2026-9

This commit is contained in:
j3d1 2026-09-02 21:40:28 +02:00
parent 9acf5a97e2
commit d00b5c7961
241 changed files with 85546 additions and 2409 deletions

View file

@ -97,9 +97,22 @@ Start the fullstack application:
docker-compose -f deploy/docker-compose.override.yml up --build
```
Run backend tests in Docker:
``` bash
docker compose -f deploy/docker-compose.override.yml run --rm backend-a bash -lc "python configure.py && python manage.py test"
```
This will start an instance of the frontend and wiki, a limited DoH (DNS over HTTPS) server and **two** instances of the backend.
The two backend instances are set up to use the domains `a.localhost` and `b.localhost`, the local DoH
server is used to direct the frontend to the correct backend instance.
The frontend is configured to act as if it was served from the domain `a.localhost`.
Access the frontend at `http://localhost:8080/`, backend at `http://localhost:8080/api/`, api docs
at `http://localhost:8080/docs/` and the wiki at `http://localhost:8080/wiki/`.
Access the frontend at `http://localhost:8080/`, backend at `http://localhost:8080/api/v1/`, api docs
at `http://localhost:8080/docs/` and the wiki at `http://localhost:8080/wiki/`.
The dev proxies terminate TLS with `frontend/.local/localhost.crt`, signed by the dev-only CA at
`frontend/.local/RootCA.crt` (regenerate both with `frontend/.local/make_ca.sh` and
`make_localhost.sh` if they've expired). Import `RootCA.crt` into your OS/browser trust store once;
without that, requests the frontend makes itself (federation calls, the DoH lookup) will fail with
opaque network errors even though clicking through the browser's own cert warning for the page you
navigated to by hand looked fine.