An Eliware infrastructure repository template for target configuration, validation, rollout, and rollback boundaries.
- Features
- Requirements
- Setup
- Usage
- Development
- Testing
- Troubleshooting
- Security
- Managed targets
- Configuration
- Target configuration
- Validation
- Change boundaries
- Support
- Links
- License
This template starts private infrastructure repositories. Each derived repository defines its managed targets and controls.
Use Node.js 26 or later and npm 12 or later for repository validation.
Create a repository from this template. Replace the template name, description, URLs, keywords, and sample content.
Run npm ci from the repository root.
Follow this README and the user guide. Read the release notes for change history.
Read AGENTS.md and the specifications index before you change files. Keep documents and records in the repository that owns them.
Run npm test before handoff. It runs the repository checks through eliware-test.
If a check fails, read the reported file path and rule.
Correct the derived repository file, then run npm test again.
Keep credentials, secrets, private data, and runtime state out of Git. Use only approved secret stores for secret values.
Name each platform, environment, purpose, and owner in the derived repository. This template defines no live target.
This template has no runtime settings. Package metadata and .knit/deploy.yaml configure repository tools.
Store committed configuration files under desired-state/. Organize them by target and environment.
Keep live status records and operating procedures in their owning repositories.
Check syntax, schemas, references, rendered output, and safety rules for the files in the derived repository. A passing check does not prove live infrastructure health.
Link to approved rollout and rollback procedures in the owning Operations or workspace repository. Do not use a commit or validation result as approval to deploy.
For help, questions, or to chat with the author and community, visit:
