olsitec/foundation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
olsitec-foundation platform repo
39 commits 1 branch 0 tags 410 KiB
Find a file
Andreas Niemann 35dc008759
All checks were successful
CI / preflight (push) Successful in 5s
Details
CI / typecheck (push) Successful in 15s
Details
ecosystem-selftest / semantic-release-bumptest (push) Successful in 13s
Details
ecosystem-selftest / eslint-gate (push) Successful in 3s
Details
ecosystem-selftest / yamllint-gate (push) Successful in 3s
Details
pulumi-preview / preview (push) Successful in 16s
Details
refactor(ci): composite actions instead of reusable workflows (Forgejo 11) 
Forgejo 11.0.15 does NOT support reusable workflows (job-level `uses:` /
`workflow_call`): the call is silently dropped and no run is scheduled (verified
live — a same-repo and a cross-repo reusable call both produced zero runs, while
an equivalent inline job ran green). The working cross-repo reuse primitive here
is the COMPOSITE ACTION referenced by FULL URL (a short-form
`uses: olsitec/foundation/...@master` resolves against the runner's
DEFAULT_ACTIONS_URL = data.forgejo.org, not the local instance, and 404s; the
full-URL form `uses: https://forge.olsitec.net/olsitec/foundation/actions/<x>@master`
was verified green).

- Replace the four reusable-*.yml with composite actions under actions/:
  node-build, docker-build, lint, semantic-release-version (same logic + inputs).
- actions/README.md documents the pattern, the Forgejo-11 limitation, and the
  999_testing candidate coverage (C2/C3/C4 self-contained; C1/C5 blocked on the
  not-yet-published @olsitec package registry).
- ecosystem-selftest paths filter: actions/** (was reusable-*.yml).

The capabilities that need no external repo (semantic-release bump sequence,
eslint/yamllint gates) keep running green via ecosystem-selftest's inline jobs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 01:14:51 +02:00
.forgejo/workflows refactor(ci): composite actions instead of reusable workflows (Forgejo 11) 2026-07-01 01:14:51 +02:00
actions refactor(ci): composite actions instead of reusable workflows (Forgejo 11) 2026-07-01 01:14:51 +02:00
backup feat(ci): baked CI image + runner config + self-check workflow (T14) 2026-07-01 00:15:01 +02:00
bootstrap feat(ci): state-dependent pulumi-preview + backup-verify pipelines (T14) 2026-07-01 00:50:16 +02:00
ci feat(ci): reusable ecosystem workflows + selftest (999_testing) 2026-07-01 01:03:56 +02:00
containers feat(ci-image): bake ecosystem CI toolchain (lint + release) 2026-07-01 01:03:55 +02:00
documentation refactor(ci): composite actions instead of reusable workflows (Forgejo 11) 2026-07-01 01:14:51 +02:00
dr feat(ci): baked CI image + runner config + self-check workflow (T14) 2026-07-01 00:15:01 +02:00
offsite-backup feat(offsite-backup): olsitec-foundation bucket + scoped creds on home MinIO 2026-06-30 20:34:55 +02:00
packages feat(provision): Phase-0 throwaway test VM via vendored @olsitec/pulumi-hetzner 2026-06-30 18:57:54 +02:00
preflight feat(preflight): host/toolchain validation + VERSIONS pin-file — T01 2026-06-30 18:00:26 +02:00
provision feat(backup): age at-rest encryption of bundles (CONTRACT_004 §4.3) 2026-06-30 23:23:38 +02:00
.gitignore feat(offsite-backup): olsitec-foundation bucket + scoped creds on home MinIO 2026-06-30 20:34:55 +02:00
bun.lock feat(bootstrap): postgres data-plane + remote helper (T03) 2026-06-30 21:10:34 +02:00
package.json feat(offsite-backup): olsitec-foundation bucket + scoped creds on home MinIO 2026-06-30 20:34:55 +02:00
README.md chore: scaffold olsitec-foundation mono-repo 2026-06-30 17:10:46 +02:00
VERSIONS feat(ci-image): bake ecosystem CI toolchain (lint + release) 2026-07-01 01:03:55 +02:00

README.md

olsitec-foundation

The self-hosting platform "egg": a single Pulumi project that brings up Forgejo (+ Actions + OCI/npm registry), PostgreSQL, HashiCorp Vault, RustFS (S3), and a reverse proxy as plain OCI containers on one VM — recoverable from {a VM, this repo, the master passphrase}.

This is Layer 0. Kubernetes, ArgoCD and everything else are Layer-1 consumers of this foundation (see ADR-004).

Layout

  • bootstrap/ — the egg Pulumi project (phases, components, config).
  • packages/ — shared, publishable Pulumi modules (@olsitec/pulumi-*).
  • preflight/ — host & toolchain validation (run before any deploy).
  • backup/, dr/ — backup + disaster-recovery automation.
  • .forgejo/workflows/ — CI (preflight, pulumi preview/up, backup-verify).
  • documentation/ — planning, ADRs, contracts, baseline overlay. Read documentation/000_baseline.md and documentation/000_TOPOLOGY.md first.

Status

Planning complete (PLAN-001 vision, PLAN-002 strategy, ADR-004/005 accepted). Implementation not yet started — next step is T00 (contracts) per PLAN-002 §10.

Recovery in one line

git clone this repo → set PULUMI_CONFIG_PASSPHRASE → ./preflight/preflight.sh → pulumi up → restore latest offsite backup. Full procedure: dr/RUNBOOK.md (TBD, task T13).