Stacks¶
Machine translation of the French original.
A stack is a deployment unit: a folder, a Compose file, a service, or a group of services that live and die together.
- Conventions — the format that a Compose file must follow here.
- Lifecycle of a stack — creation, modification, starting on boot, shutdown.
- Continuous integration — Gitea Actions, the scope of a runner, and deploying without giving a shell.
Where to find the actual configuration¶
| Question | Fastest Answer |
|---|---|
| What memory limit, what port, what image? | 00-infra/stack-config-snapshot.md in the vault — auto-generated, no SSH required |
| What is running, what is stopped? | 00-infra/_generated-overview.md, regenerated daily at 18:35 |
| On which host is this container running? | 00-infra/docker-inventory.md |
| Why is this stack configured this way? | 10-stacks/<nom>/decisions.md |
The name of a container is not always the name of its Compose folder. The base image runs in wikijs-db, in the folder wikijs. Searching for a folder by container name often fails.
Dernière vérification de cette page : 2026-09-29