docs: capture exploration — backend-deployment

This commit is contained in:
Jakub Zych
2026-09-28 01:27:19 +02:00
parent cbb5a516ef
commit a64d5aaaa7
5 changed files with 100 additions and 0 deletions

View File

@@ -0,0 +1,20 @@
---
title: Nest framework packages under modules/ — same beach names
date: 2026-09-28
priority: high
area: summercms.go
---
Mechanical layout change only. Do not rename packages.
Move each framework library from the repo root into `modules/<name>/` so `ls` shows `modules/`, `cmd/`, `admin/`, `examples/`, `internal/` instead of `compass` next to `go.mod`.
In scope (beach-named libs and peers): backpack, boardwalk, bonfire, bouncer, cabana, compass, festival, fetchguard, lagoon, pact, party, phrasebook, postcard, surf, tide, towel, wire, wristband.
Stay at repo root: `admin/`, `cmd/`, `examples/`, `internal/`, `scripts/`, `go.mod`, `README.md`.
Import paths become `git.golem15.com/golem15/summercms/modules/<name>`. Rewrite importers in this repo, `../fonoteka.go` (~124 files), and `examples/`. Then `go test ./...` in both repos.
Do this before Phase 11 adds more root packages. Do not remap onto Winter `system` / `backend` / `cms`.
After the move is green, run the sibling todo that writes a short `README.md` per module.

View File

@@ -0,0 +1,14 @@
---
title: Short README.md per modules/* after the nest
date: 2026-09-28
priority: medium
area: summercms.go/modules
---
Blocked on `.planning/todos/pending/nest-framework-packages-under-modules.md`.
After the packages live under `modules/`, spawn a GSD explore / researcher pass (one agent, not a hand-written dump) to write a short `README.md` in each `modules/<name>/`.
Each file: one paragraph on what the package is for, who imports it, and one example entry point (`Package.Type` or file). No architecture essays. No copy-paste of planning docs.
The top-level `summercms.go/README.md` should then link the directory instead of explaining every beach name inline.

View File

@@ -0,0 +1,14 @@
---
title: Refresh fonoteka.go README — short status plus migrate/serve/login
date: 2026-09-28
priority: high
area: ../fonoteka.go/README.md
---
Keep this file a short run card. Do not duplicate the framework story.
Update status from "Phase 3 vertical slice / 15 genres" to what actually runs: `golem15.user` + `golem15.fonoteka`, Postgres with Polish ICU `pl-PL`, `./bin/fonoteka migrate` then `serve`, admin SPA login at the configured admin prefix.
Keep the existing DSN / JWT secret / collation block. Add the minimum env and URL needed to log in the way it already worked. Point at `../summercms.go/README.md` for architecture and the plytarium.com cutover picture.
Lives in the sibling repo; planning docs stay in `summercms.go`.

View File

@@ -0,0 +1,18 @@
---
title: Rewrite summercms.go README — onboard, recreate login, honest cutover
date: 2026-09-28
priority: high
area: summercms.go/README.md
---
Replace `README.md`. It currently says pre-alpha / nothing runs. That is false.
The long story lives here, not in `fonoteka.go`. Include:
- What this repo is (framework only; app is the sibling `fonoteka.go`).
- Two-repo layout and `go.work` replace during development.
- How to recreate the Phase 10 admin login that already worked (point at `fonoteka.go` for DSN / migrate / serve; do not pretend this repo is the app binary).
- Current status vs the Phase 15 PHP flip — honest "not yet" cutover section drawn from `.planning/notes/go-vs-php-on-plytarium.md`.
- After the `modules/` nest lands, point at `modules/<name>/README.md` instead of listing beach-named packages at the repo root.
Do not invent a production runbook. Operator procedure stays in the PHP `docs/deploy/plytarium.com.md` until Phase 15.