SECURITY.md says where to report a problem ([email protected]) and what's in scope. The README points at docs.cairnobs.org for people installing Cairn OBS. The tests, examples and notes named a real fleet: its host names, its mesh and desk link, a public address, its site and its backups. They're now node1, node2 and so on, wg-desk, 10.30/10.31, 203.0.113.52 (TEST-NET-3), Lisbon, wiki-db and photos. docs/install.md's Windows paragraph said no VMs; the agent now reports certificate stores, the event log and Hyper-V's VMs, on amd64 and arm64.
21 lines
591 B
YAML
21 lines
591 B
YAML
# What should run where. Patterns match Docker container names; * matches
|
|
# any run of characters. See docs/formats.md.
|
|
#
|
|
# The real file is written from each host's `docker ps -a` when Cairn OBS is
|
|
# first deployed, then kept up to date in this repo.
|
|
|
|
hosts:
|
|
node2:
|
|
running:
|
|
- wiki-*
|
|
- discourse
|
|
- inbuxa-admin
|
|
- inbuxa-demo
|
|
stopped:
|
|
- match: cairnobs-demo-*
|
|
note: Paused since 2026-09-18 while cairnobs development is on hold.
|
|
|
|
# CI job containers come and go. They are counted, never listed or alerted on.
|
|
ci_jobs:
|
|
- GITEA-ACTIONS-TASK-*
|