j3d1/toolshed
2
1
Fork 0
Code Issues 9 Pull requests 1 Projects Releases Packages Wiki Activity

stash

Browse source
This commit is contained in:
j3d1 2026-08-27 00:37:32 +02:00
parent 9f3dc7c993
commit f46eff65fd
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/development.md
View file

@ -108,4 +108,11 @@ The two backend instances are set up to use the domains `a.localhost` and `b.loc
server is used to direct the frontend to the correct backend instance. 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`. 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 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/`. 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.