kevinveenbirkenbachandClaude Opus 5
ac7b98f342
scripts/tests/environment/ becomes scripts/tests/workspace/ with one subdirectory per track. base/ prepares the workspace and is a prerequisite; compose/ and swarm/ are independent of each other, so CI can run them as separate jobs with a budget each. 00_orchestrator.sh runs the tracks named by INFINITO_WORKSPACE_TRACKS and aborts on an unknown one. The job count stays at five: cli.meta.ci.dev_runtime matrix assigns exactly one track per distro and flips the split with the run number, so two consecutive runs cover both tracks on every distro without doubling the matrix. The workspace_track input (rotate|compose|swarm) pins it from manual steer through the orchestrator for a targeted re-run. Job names carry the track glyph from utils/symbol_glossary and the image shortened to its last two segments, so quay.io/centos/centos:latest reads as centos:latest. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.2 KiB
Installation Guide 🚀
Use this guide to install the infinito CLI with the method that fits your workflow.
Run with Docker 🐳
Build the image and run the CLI. For more options, see Docker and Runtime Commands.
docker build -t infinito:latest .
docker run --rm -it infinito:latest infinito --help
Develop from Source 💻
Clone the repository and install the project from the repository root:
git clone https://github.com/infinito-nexus/core.git
cd core
make install
make environment-bootstrap
This prepares the repository for local development.
make environment-bootstrap also installs the repository's local pre-commit hooks for this checkout.
All available make commands are documented in the Makefile Commands reference.
For a worked example of how these commands interact (including build, bootstrap, test, deploy, and teardown), see the environment test suite.
For further information on setting up a local development environment, see CONTRIBUTING.md.
For inventory creation and deployment, continue with the Deploy Guide.