[Feature]: Install file to facilitate installation

[grazrib]

Problem or Motivation

• install.sh exists to make startup deterministic and repeatable, avoiding known errors caused by manual setup.
• It centralizes critical pre-checks (required tools, Docker availability, required files) and fails fast with clear messages.
• It generates/normalizes .env consistently, reducing crashes from missing or malformed variables (e.g., DATABASE_URL/password).
• It prepares bind-mounted directories (data, credentials, config) with correct permissions, preventing runtime PermissionError.
• It reduces environment drift across dev/test/prod by applying the same bootstrap sequence every time.
• It lowers operational burden for developers: fewer manual steps, fewer intermittent errors, faster onboarding.

Proposed Solution

File install.sh

install.sh

Alternatives Considered

No response

Area

Core / Architecture

Additional Context

System Version Ubuntu 22.04.5 LTS
Architecture aarch64
Kernel Version 6.8.0-1041-oracle
CPU Core 4
Memory Size 23.42 GB
Docker Version 28.5.1

[dcorio]

Thanks for the proposal — we agree and the design is already approved internally (spec dated 2026-04-17). The shape:

• Two scripts, setup.sh (bash, Linux/macOS) and setup.ps1 (PowerShell 5.1+, Windows), same 8-step flow
• Pre-checks: Docker daemon reachable, docker compose v2 available (link to official install docs on failure — the scripts don't install Docker themselves)
• Template bootstrap: copy .env.example → .env and docker-compose.yml.example → docker-compose.yml only if the targets don't already exist (idempotent — re-running on an existing install never overwrites operator customisations)
• Secret generation: populate missing POSTGRES_PASSWORD, INTERNAL_API_SECRET, EXECUTOR_TOKEN in .env via openssl rand (keeps existing values untouched)
• Prompt for GRIDBEAR_BASE_URL with http://localhost:8088 as default
• Interactive confirmation before docker compose up -d --build
• Health check poll (max 60s) and success message with URL to /auth/setup

Out of scope for the script: installing Docker/proxies/TLS, configuring bot tokens, creating the first admin user (GridBear handles that at /auth/setup on first access).

Implementation will follow — tracked by this issue. Keeping it open until setup.sh / setup.ps1 land.