Files
computer-playbook/docs/administration/installation.md
T
kevinveenbirkenbachandClaude Opus 4.7 f20278b4d5 refactor(env): drop env.development marker and its compose layering
The env.development marker file existed for two purposes that no longer
justify the wiring cost: a per-machine compose --env-file override layer
appended after auto-loaded .env, and a fallback signal for
detect_runtime() to return "dev" when the marker exists. With every
INFINITO_* default now collapsed into env/default.env -> .env,
persistent per-machine overrides are best expressed as
\`export INFINITO_FOO=…\` before invoking make (load.sh honors
caller-set values via setdefault). The marker fallback in
detect_runtime was redundant with the explicit RUNTIME=dev that every
dev-flow callsite already passes (fresh-*.sh, reset/inventory.sh).

Removed:
- Makefile mark-development target + .PHONY entry
- env.development from .gitignore / .dockerignore
- env_local conditional in compose.up()
- env_development conditional in down._compose_run()
- env.development conditional in scripts/meta/resolve/apps.sh and
  scripts/meta/resolve/diff/affected_roles.sh
- env.development marker branch + the now-unused project_root parameter
  from cli/meta/runtime/detect_runtime; __main__.py caller follows
- "Optional Development Marker" section in docs/contributing/environment/
  setup.md and the marker reference in docs/administration/installation.md

Also drops two RUNTIME=='dev' guards in roles/web-app-bigbluebutton that
relied on the auto-detect path:
- the compose build etherpad task in tasks/02_compose.yml
- the freeswitch iptables-REJECT entrypoint override in
  templates/compose.override.yml.j2

With auto-detection of "dev" gone the guards would otherwise only fire
on explicit RUNTIME=dev runs, silently regressing the local-dev path
operators rely on; both behaviors now apply unconditionally.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-21 16:22:33 +02:00

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.