generated from coulomb/repo-seed
94 lines
2.4 KiB
Markdown
94 lines
2.4 KiB
Markdown
# Decision Log
|
|
|
|
_Auto-generated by the Custodian State Hub._
|
|
|
|
## State Hub workstation Postgres migration approval
|
|
|
|
**Date:** 2026-06-03
|
|
**Decided by:** codex
|
|
|
|
Superseded by WP-0004 T09 cancellation and CUST-WP-0038 ownership of State Hub HA migration, including hostname, registry, exposure model, HA database/storage, restore drills, and production data migration approval.
|
|
|
|
---
|
|
|
|
## activity-core deployment architecture
|
|
|
|
**Date:** 2026-06-03
|
|
**Decided by:** codex
|
|
|
|
Superseded by completed WP-0004 outcome: activity-core was deployed as a K3s production service on railiance01 on 2026-05-22; the packaging architecture question is no longer blocking this workplan.
|
|
|
|
---
|
|
|
|
## Review CCR-2026-0001 whynot-design npm publish token lane
|
|
|
|
**Date:** 2026-06-27
|
|
**Decided by:** human
|
|
|
|
APPROVE: scoped path and confirmed binding are acceptable
|
|
|
|
---
|
|
|
|
## Review CCR-2026-0001 corrected whynot-design npm publish token lane
|
|
|
|
**Date:** 2026-06-27
|
|
**Decided by:** human
|
|
|
|
APPROVE: We fixed the path using coulomb as the org/tenant.
|
|
|
|
---
|
|
|
|
## Forgejo hostname and exposure model
|
|
|
|
**Date:** 2026-07-02
|
|
**Decided by:** human
|
|
|
|
the hostname shall be forgejo.coulomb.social. The exposure model is private repos by default. We will use the transition from gitea to forgejo for closing down public access and establishing credential handling to have convenience when working with the repos. Gitea can and should remain reachable during transition.
|
|
|
|
---
|
|
|
|
## Forgejo SMTP and sender identity
|
|
|
|
**Date:** 2026-07-02
|
|
**Decided by:** human
|
|
|
|
We will use forgejo@coulomb.social
|
|
|
|
---
|
|
|
|
## Forgejo package registry scope
|
|
|
|
**Date:** 2026-07-02
|
|
**Decided by:** human
|
|
|
|
We should support the full range from the start.
|
|
|
|
---
|
|
|
|
## Forgejo Actions runner isolation model
|
|
|
|
**Date:** 2026-07-02
|
|
**Decided by:** human
|
|
|
|
we will try to go with isolated host runners, with least-privilege credential boundaries.
|
|
|
|
---
|
|
|
|
## Forgejo backup target and restore cadence
|
|
|
|
**Date:** 2026-07-02
|
|
**Decided by:** human
|
|
|
|
We will need to figure out the details, but i want to use backup.coulomb.social as the hostname with a backend we need to figure out yet.
|
|
|
|
---
|
|
|
|
## Forgejo cutover and rollback strategy
|
|
|
|
**Date:** 2026-07-02
|
|
**Decided by:** human
|
|
|
|
We will do a staged migration and lock the gitea repos of transitioned repos but keep gitea until everything has been transfered and just then start a 14day trial phase and after that retire gitea to the backup.
|
|
|
|
---
|