docs: add inbox items from marathon sprint (multi-node, prioritize small)
This commit is contained in:
@@ -400,5 +400,7 @@ When multiple agents work on the same repo, use git worktrees instead of branche
|
|||||||
|
|
||||||
- **Least-privilege agent access**: Agents should SSH as a dedicated non-root user (e.g. `deploy@`) with scoped sudo for only what they need (systemctl, caddy reload). No root SSH long-term.
|
- **Least-privilege agent access**: Agents should SSH as a dedicated non-root user (e.g. `deploy@`) with scoped sudo for only what they need (systemctl, caddy reload). No root SSH long-term.
|
||||||
- **Immutable deploy artifacts**: Agent builds a tarball/image, uploads it, runs a deploy script. Never edits files in-place on production.
|
- **Immutable deploy artifacts**: Agent builds a tarball/image, uploads it, runs a deploy script. Never edits files in-place on production.
|
||||||
|
- **Multi-node same-repo**: Multiple workers (laptop + vserver) working on same git repo but different features. Merge conflicts → Gitea Actions hook or team-lead merge strategy. Start small: one worker per repo. Scale: worktrees per feature.
|
||||||
|
- **Prioritize small+working over ambitious+broken**: "Lieber erstmal klein und funktionierend und dann mehr." Collect ideas, implement incrementally, never ship broken.
|
||||||
|
|
||||||
_Drop new principles here. They get organized on next pass._
|
_Drop new principles here. They get organized on next pass._
|
||||||
|
|||||||
Reference in New Issue
Block a user