docs(docs): Ubuntu native development, Docker for services and isolation, separate VPS; pnpm check:all; CI status
RUST.md §1 (three environments, native install recipe, what stays in Docker and why), §4 (pre-merge gate, workflow files prepared and never run), §5.8 (native run numbers against the builder image), §6; CLAUDE.md stack row, commands, map, workflow rule; README quick start and verification; DEPLOY.md CI status; WORKSPACE.md; TEST_STRATEGY.md; CHANGELOG; review Annex C.1 addendum of 2026-10-13.
This commit is contained in:
1 parent
981a66f33b
commit
6e2bbec4b0
8 files changed
+233
-68
No files matched your search
@@ -25,8 +25,11 @@ Rust (plan R0, `docs/development/RUST.md`): the repository also builds a
|
||||
worker image (`crates/worker/Dockerfile`, static musl binary on
|
||||
`distroless/static`, container `faunosteo_worker`). It is not deployed yet
|
||||
(its job loop arrives at R1); the live deployment above is unchanged. The
|
||||
production VPS never needs a Rust toolchain: images are built in CI and
|
||||
pulled by digest ("Image deploy by digest", prepared below).
|
||||
production VPS never needs a Rust toolchain: Rust is compiled on the Ubuntu
|
||||
development machine (native toolchain) or inside Docker builder images, and
|
||||
production images will be pulled by digest ("Image deploy by digest",
|
||||
prepared below) once a runner and a registry exist on the forge. No CI/CD is
|
||||
operational today (2026-10-13).
|
||||
|
||||
### Reference sheet in the image (SHEET_BUNDLE)
|
||||
|
||||
@@ -582,7 +585,9 @@ deployment keeps building on the VPS as documented above.
|
||||
|
||||
1. Build and publish: run the manual workflow `release-images`
|
||||
(`.gitea/workflows/release-images.yml`, `workflow_dispatch`, never on
|
||||
push) on the forge. It pushes `faunosteo_app:<sha>` and
|
||||
push) on the forge. Prerequisite not met yet: no runner, registry or
|
||||
secret is configured on the forge (2026-10-13); the workflow has never
|
||||
run, which is the CI/CD step to decide separately. It pushes `faunosteo_app:<sha>` and
|
||||
`faunosteo_worker:<sha>` to the container registry named by the
|
||||
`REGISTRY` secret (the forge's own Gitea registry is the recommended
|
||||
choice, Scaleway Container Registry the alternative) and prints their
|
||||
|
||||
Reference in new issue
Block a user