feat: one-command install wizard (curl | bash → ordo init)#123
Merged
Conversation
Add a real first-time-install path: a curl-able install.sh bootstrap that checks prereqs, clones, installs the ordo CLI into a venv, and launches a comprehensive interactive wizard that takes a fresh operator from nothing to a running stack. - ordo/wizard.py: rewritten. Detect hardware -> confirm best-fit model -> toggle capability groups (image-video/rag/voice/automation/search/monitoring, chat always on) -> tailnet hostname + Caddy bind -> Google SSO (client id/secret + email allowlist) -> secrets. Internal secrets auto-generated (LITELLM_MASTER_KEY/OPS_CONTROLLER_TOKEN/MCP_GATEWAY_TOKEN/cookie/SEARXNG/n8n); external ones (Google/HF/Tailscale/GitHub) prompted + skippable. Writes <out>/ordo.yaml + <out>/secrets.env (chmod 600) and the oauth2-proxy allowlist. Pure logic (build_source / plugins_from_capabilities / resolve_secrets) kept testable; secret KEY set is data-driven from render(). - ordo/cli.py: add `ordo init` (setup kept as alias). Live-tree overwrite guard; post-wizard render/fetch/up offers (each y/N); prints dashboard URL. Under --yes/non-interactive it only writes config, never brings up. - install.sh: POSIX sh bootstrap with the curl one-liner, prereq checks (git/docker/compose/python3.11+, nvidia-smi warn), idempotent clone + venv. - tests: new answers-schema + capability/secret-mapping coverage; headless write->render round-trip. - README: leads with the curl one-liner + what the wizard asks. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Read prompts from /dev/tty (both the install-dir ask() and the wizard's own stdin) instead of the script's stdin. Under `curl … | sh` stdin is the piped script, not a terminal, so the previous `[ -t 0 ]` check fell through to non-interactive `ordo init --yes` (config-only) — the exact opposite of the one-curl-drives-the-whole-wizard goal. /dev/tty still reaches the real console, so a piped install is now fully interactive; genuinely headless runs (no /dev/tty, e.g. CI) still degrade to --yes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Both docs opened with config-as-render philosophy (and the operator guide with a 30-item build log) before ever saying how to install. Restructure so the one-curl install and the interactive `ordo init` wizard are the lead: the wizard's six steps (hardware/model/capabilities/access/SSO/secrets) are now the centerpiece, with the manual render path kept below as the alt. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the missing first-time-install experience: a single curl-able bootstrap that launches a comprehensive interactive wizard taking a fresh operator from nothing to a running stack.
curl -fsSL https://raw.githubusercontent.com/AlienWalker1995/Ordo-AI-Stack/main/install.sh | shWizard decision flow
hardware.detect().summary()(accept or pin later)catalog.best_fit(hw)recommendationautoautodefaultplugins:list when customizedtailscale ip -4(if present)CADDY_TAILNET_HOSTNAME,CADDY_BIND(tailnet-IP vs 0.0.0.0); offerstailscale certCADDY_TAILNET_DOMAINderived from hostauth/oauth2-proxy/emails.txtrender()Writes
<out>/ordo.yaml(source) +<out>/secrets.env(chmod 600, gitignored, never committed).ordo initpost-wizard offers (interactive only, each y/N)ordo render --source <out>/ordo.yaml --out <out>ordo fetchcd <out> && COMPOSE_PROFILES=<selected> docker compose -p ordo --env-file .env --env-file secrets.env up -d, then printshttps://<host>:8444/.Safety
--yes/ non-interactive writes config only — never renders, never brings the stack up.ordo initrefuses to clobber an existing<out>/ordo.yamlorsecrets.envwithout--force.setupkept as an alias ofinit.What's auto vs prompted vs generated
render()— no hardcoded drift).Validation
ordo init --yes --out $TMP/wiz→ validordo.yaml+secrets.env(11 keys, 6 generated non-empty, 5 external blank);ordo renderfrom the temp source succeeds (ctx consistency OK).sh -n install.shclean.ruff check .clean;pytest tests/= 564 passed, 4 skipped.out/never written (mtimes pre-session); live source still renders to a temp dir.Not fully automated (guided instead)
https://<host>/oauth2/callback) and collects the resulting id/secret.tailscale cert— offered only whentailscaleis on PATH; otherwise it prints the manual command.🤖 Generated with Claude Code