olsitec/foundation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
olsitec-foundation platform repo
41 commits 1 branch 0 tags 410 KiB
Find a file
Andreas Niemann 290f48ba18
All checks were successful
CI / preflight (push) Successful in 4s
Details
CI / typecheck (push) Successful in 15s
Details
ecosystem-selftest / semantic-release-bumptest (push) Successful in 12s
Details
ecosystem-selftest / eslint-gate (push) Successful in 4s
Details
ecosystem-selftest / yamllint-gate (push) Successful in 4s
Details
pulumi-preview / preview (push) Successful in 18s
Details
revert(ci): reusable workflows after all — Forgejo 11 supports them 
Correction to the previous commit. Forgejo 11.0.15 DOES support reusable
workflows; my earlier "not supported" was a false negative — the test caller
omitted `runs-on`, and the pre-v15 "limited" implementation REQUIRES `runs-on`
on the calling job (omitting it makes Forgejo silently schedule no run). Verified
live: a caller with `runs-on` runs green, same-repo and cross-repo (short ref);
the full-URL form fails for reusable workflows (it was only needed for composite
ACTIONS, which resolve via DEFAULT_ACTIONS_URL).

- Restore the four reusable-*.yml (on: workflow_call), the architecture the
  handover + 999_testing chose; fix the caller examples to include `runs-on`.
- Remove the composite-action layer (actions/) — single mechanism, no redundancy.
- .forgejo/workflows/README.md documents the v11 caller-`runs-on` + short-ref
  quirks (both removed by a future Forgejo v15 upgrade) and the candidate coverage.
- ecosystem-selftest paths filter back to reusable-*.yml.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 01:48:29 +02:00
.forgejo/workflows revert(ci): reusable workflows after all — Forgejo 11 supports them 2026-07-01 01:48:29 +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 docs(session): SESSION_2026-07-01_002 — T14 done + ecosystem CI (999_testing) 2026-07-01 01:18:32 +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).