-
-
Notifications
You must be signed in to change notification settings - Fork 0
Installation and Operations
This page is explanatory. The canonical installation guide is
INSTALL.md.
Use the repository bootstrap to restore the pinned Hermes runtime and the MiniCISO overlay. Keep exact flags, limits, and platform-specific edge cases anchored to INSTALL.md.
This page is the short operator map for:
- prerequisites;
- quick install;
- platform variants;
- provider/model setup;
- bootstrap behavior;
- validation and smoke testing;
- update and rollback;
- common operational issues.
git clone https://github.com/icidade/miniCISO.git
cd miniCISO
.\scripts\bootstrap.ps1git clone https://github.com/icidade/miniCISO.git
cd miniCISO
./scripts/bootstrap.sh- Windows: use the PowerShell bootstrap and validation scripts.
- Linux/macOS/WSL: use the Bash scripts.
- VPS: keep private state outside the public repository and review diffs carefully before publishing safe exports.
Provider setup is interactive because credentials do not belong in Git. MiniCISO assumes the user keeps those credentials in the Hermes environment rather than in this repo.
Bootstrap restores the pinned runtime, creates the profile set, installs prompts and templates, prepares the workspace, and runs structural checks.
Offline validation:
./scripts/validate-repo.shOnline smoke test:
./scripts/smoke-test.sh --onlineUse online mode only when you want to spend provider tokens to verify profile responses.
- Update instructions:
INSTALL.md#updating-the-overlay - Rollback instructions:
INSTALL.md#rollback
MiniCISO is an overlay. Some runtime dependencies, provider support, and isolation properties are inherited from Hermes and the host environment.
If bootstrap or validation fails, start with: