https://www-staging.alwaldend.com/docs/infra/forgejo/ Recent content in forgejo on Alwaldend Hugo en https://www-staging.alwaldend.com/docs/infra/forgejo/openspec/specs/infra-forgejo/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/infra/forgejo/openspec/specs/infra-forgejo/spec/ <h1 id="forgejo-infrastructure-specification">Forgejo infrastructure specification<a class="td-heading-self-link" href="#forgejo-infrastructure-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Describe the Forgejo service owned by <code>infra/forgejo</code>, including Xen Orchestra provisioning, Ansible service configuration, and Terraform account and repository management. The <code>tf_setup</code>, <code>ansible</code>, and <code>tf</code> packages are implementation stages of this owner. This baseline records source guarantees and prerequisites; it does not verify live service health or restore earlier Forgejo data.</p> <p>Baseline revision: <code>550d7e79b1f5fdbc2b6017b75178471d6914082f</code>. Observed: 2026-09-08. Sources: <a href="https://www-staging.alwaldend.com/docs/infra/forgejo/">owner README</a>, <a href="../../../BUILD.bazel">BUILD</a>, and the implementation links below.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-scoped-xen-orchestra-provisioning-and-disk-checks">Requirement: Scoped Xen Orchestra provisioning and disk checks<a class="td-heading-self-link" href="#requirement-scoped-xen-orchestra-provisioning-and-disk-checks" aria-label="Heading self-link"></a></h3><p>Setup SHALL provision Forgejo through Xen Orchestra in the <code>src_infra_dc1_forgejo1</code> resource set using the owner&rsquo;s Vault AppRole and packaged XO OIDC login flow. The VM SHALL declare 20 GiB boot, 40 GiB Forgejo, and 5 GiB Traefik disks. Ansible SHALL verify the expected sizes of <code>xvdb</code> and <code>xvdc</code> before applying the service roles that use them.</p> https://www-staging.alwaldend.com/docs/infra/forgejo/openspec/specs/owned-dns/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://www-staging.alwaldend.com/docs/infra/forgejo/openspec/specs/owned-dns/spec/ <h1 id="owned-dns-specification">owned-dns Specification<a class="td-heading-self-link" href="#owned-dns-specification" aria-label="Heading self-link"></a></h1><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Define Forgejo DNS management through the owner&rsquo;s <code>tf_setup</code> root, including canonical declarations, scoped credentials, and offline source checks before adopting live records.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-owner-local-dns-configuration">Requirement: Owner-local DNS configuration<a class="td-heading-self-link" href="#requirement-owner-local-dns-configuration" aria-label="Heading self-link"></a></h3><p>The <code>tf_setup</code> root SHALL consume this owner&rsquo;s canonical <code>dnsconfig.json</code> through the shared DNS Terraform module, preserving declared record identities and views. DNS resources SHALL default to disabled before adoption and SHALL remain enabled by default after authorized adoption. Adoption SHALL bind existing provider records to the owner&rsquo;s state without adding, changing, replacing, or deleting DNS records. Subsequent reconciliation of unchanged declarations SHALL preserve owned and unrelated records.</p>