Workstations, devcontainers and operations
These guides are for the operator: installing the engine on a workstation, building devcontainers, moving work between machines, and supplying the operational configuration the engine acts on.
Read Workstation install and status first.
- Workstation install and status:
praetorctl workstation installandstatuson every operating system. - Portable DevContainer bootstrap: building a devcontainer from an explicitly selected Praetor source snapshot.
- Local repository observations: the workstation harvester's private report of local Git repositories.
- Workstation sync with devsync: moving project folders between workstations through rclone and Google Drive.
- Operational configuration: which settings belong to the engine and which the operator supplies.
- Operational fork synchronization: the
init,planandpreparestages ofpraetorctl operational sync. - Admission for heavy local steps:
praetorctl admit, which holds a heavy step until the host has memory, swap and load headroom and runs it in its own systemd scope.