Caret Rules (Human Guide) | 한글
This document is a human-readable companion to .agents/context/caret-rules.json.
It summarizes how to work on this repo safely, especially in production.
- This is a production host. Prefer minimal, targeted changes.
- Never commit secrets. Do not add
.env*,certs/,*.pem, or runtime keys to git. - Keep runtime
nginx.conffiles untracked; publishnginx.conf.sampleinstead. - Runtime-critical areas require documentation of changes and intent:
hubs-all-in-one/xrcloud-backend/xrcloud-frontend/xrcloud-nginx/
- Cert/key files must be real files, not directories.
- Validate with
fileoropenssl x509when diagnosing TLS issues. - If restoring from backups, ensure paths align with
.env.prodand run scripts.
- Use
git submodule update --init --recursivefor fresh clones. - If a submodule commit is missing upstream, coordinate to push or move to an available commit.
- Keep human docs in
docs/(Korean and English paired). - Reference this file from README(s) for visibility.
- For ops history and recovery steps, see
docs/ops-status.mdanddocs/ops-recovery-plan.md.