Deploy rodecomp from the clank-together checkout only

This commit is contained in:
ragnarok-clanker 2026-10-26 15:53:42 +01:00
commit 13c907b350

View file

@ -1,9 +1,9 @@
# Ragnarok deployment on memento
Deployment files: `C:\Users\Memento\Desktop\rodecomp`; Compose file:
`deploy/rodecomp/compose.yaml`. All services and compiler execution run in Linux
Docker containers. Persistent repository, SQLite, targets and downloads live in
the external Docker volume `rodecomp_data` (create it before Compose).
Single source: the git checkout `C:\Users\Memento\Desktop\clank-together` (this
repository). Compose file: `deploy/rodecomp/compose.yaml`. All services and compiler
execution run in Linux Docker containers. Persistent repository, SQLite, targets and
downloads live in the external Docker volume `rodecomp_data` (create it before Compose).
The pinned candidate toolchain is MSVC **19.29.30159**, v142, x86 target, Windows
SDK **10.0.19041.0**, under Wine. This is consistent with Ragexe's linker 14.29
@ -31,8 +31,10 @@ localhost port. Caddy strips `/git/` and forwards it to Forgejo; other paths go
to Clank. Generated installers use the configured public HTTPS hostname.
Do not publish the Desktop directory or Docker socket.
From memento's Debian WSL, start/restart with:
`docker compose -f /mnt/c/Users/Memento/Desktop/rodecomp/deploy/rodecomp/compose.yaml up -d`.
From memento's Debian WSL, after `git pull --ff-only` in that checkout, build and start with:
`docker compose -f /mnt/c/Users/Memento/Desktop/clank-together/deploy/rodecomp/compose.yaml up -d --build`.
Publish new td binaries with `deploy/rodecomp/Dockerfile.client` (output copied to
`rodecomp_data/downloads`); the installers pick up their SHA-256 on the next request.
Back up the volume with the services stopped, including SQLite and repository;
copying only the Desktop deployment files does not back up runtime state.