complete codex docs
This commit is contained in:
parent
b5dcf01a8c
commit
3cefad183d
62 changed files with 2730 additions and 50 deletions
29
docs/decisions/0001-screen-vs-tmux.md
Normal file
29
docs/decisions/0001-screen-vs-tmux.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
# Decision 0001: Keep `screen` As The Shared Backend
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Decision
|
||||
|
||||
GSP should keep `screen` as the shared process/session backend for both Linux and Windows/Cygwin agents for the current platform generation.
|
||||
|
||||
## Reasoning
|
||||
|
||||
- The existing agents already implement server lifecycle around `screen`.
|
||||
- Linux and Windows/Cygwin behavior can stay aligned if both sides share the same session model.
|
||||
- The Panel already expects session-based lifecycle checks.
|
||||
- Moving to a different backend too early would create a large amount of compatibility work for start/stop/restart, logging, and scheduler flows.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
- `tmux`
|
||||
- direct process supervision without session wrappers
|
||||
- custom daemon per server
|
||||
|
||||
## Why Those Were Not Chosen
|
||||
|
||||
- They would require broader code changes across both agents and the Panel.
|
||||
- The existing runtime, log, and scheduler flows already assume `screen`.
|
||||
- Cross-platform parity is easier to maintain with the current backend.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue