Keep · infra SKILL.md
Cloud Agent environment.json: install vs start vs terminals + Dockerfile
WhenUse when a Cloud Agent Build must be shared and long-running processes must survive the snapshot.
StopNever start Docker/DBs in install. Never leave secrets in the committed JSON.
Steps
- Resolution order: .cursor/environment.json in the repo → personal saved env → team saved env.
- Commit this so the whole team (and automations) share one Build.
- | Command | When | Put here | |---|---|---| | install | During each Build | deps, codegen, compile, cache warmup.
- Do not start Docker/DBs in install — processes die when the Build snapshots.
- Paths in build are relative to .cursor.
- Add live processes (documented in setup + builds):
Load.cursor/environment.json. Dockerfile optional. Repo only.
--- name: Cloud Agent environment.json: install vs start vs terminals + Dockerfile description: Use when a Cloud Agent Build must be shared and long-running processes must survive the snapshot. --- # Cloud Agent environment.json: install vs start vs terminals + Dockerfile When: Use when a Cloud Agent Build must be shared and long-running processes must survive the snapshot. Stop: Never start Docker/DBs in install. Never leave secrets in the committed JSON. 1. Resolution order: .cursor/environment.json in the repo → personal saved env → team saved env. 2. Commit this so the whole team (and automations) share one Build. 3. | Command | When | Put here | |---|---|---| | install | During each Build | deps, codegen, compile, cache warmup. 4. Do not start Docker/DBs in install — processes die when the Build snapshots. 5. Paths in build are relative to .cursor. 6. Add live processes (documented in setup + builds): Load: .cursor/environment.json. Dockerfile optional. Repo only.
