mirror of
https://github.com/dredx/prole.git
synced 2026-09-23 12:03:59 +00:00
553612bdff
- Delete tracked knoe-db/.prole_user_password (dead secret, rotated in ansible since the original commit) - Remove postgres-password.txt and build/ copy from working tree - Add explicit ignore rules for *_password, postgres-password*, .prole_user_password, *-secret variants Add docs/plans/customer-deploy-resync.md with the upstream/downstream migration plan and update CLAUDE.md to reflect prole's role as a customer deploy of knoe-db. |
||
|---|---|---|
| .. | ||
| customer-deploy-resync.md | ||
| README.md | ||
Plans (prole — customer deploy)
This directory holds plans specific to the prole.org customer deployment of the knoe.dev platform.
What lives here
| File | Purpose |
|---|---|
customer-deploy-resync.md |
The active plan to converge this working tree onto knoe-db/main as a long-lived customer branch. |
What does not live here
Platform-level plans live upstream in ~/dev/knoe-db/docs/plans/:
knoe-auth-round-1.md— Kerberos identity + invite-OTP enrollment + TOTP. Architectural reference.deployment-modes.md— Four-mode installer + welcome-screen selector. Architectural reference.
(Paths above are relative to your ~/dev/ root. If you're reading this on the file server, navigate to the knoe-db checkout.)
Why the split
prole is being converged into a customer-deploy branch in knoe-db, not a separate fork. Platform docs travel with the platform code (in knoe-db); customer-deploy-specific docs travel with the customer branch (here). When the customer branch is published in knoe-db, this directory will move with it.
See the upstream ~/dev/knoe-db/docs/plans/README.md for the full conventions on writing plans, plan statuses, and how customer deploys are structured.