make preflight

Introduction

make preflight runs the host checks of scripts/preflight_cli.sh and nothing else. It starts no container and changes nothing. Run it before make setup to confirm Docker is up and the .env is healthy.

make preflight
🩺 SPLENT CLI pre-flight

  [✔] Docker installed, Docker version 29.2.1, build a5c7197d72
  [✔] Docker daemon is running (reachable without sudo)
  [✔] Docker Compose v2 available, 2.38.1
  [✔] Git identity configured, Your Name <you@example.com>
  [✔] ~/.ssh present
  [✔] No duplicate variables
  [✔] No malformed lines
  [✔] SPLENT_HOST_PROJECT_DIR = /home/me/splent_workspace
  [✔] WORKING_DIR = /workspace
  [✔] SPLENT_APP unset (detached mode)
  [✔] No drift versus .env.example

✅ Pre-flight passed.

It exits 1 on a hard problem and 0 otherwise. make setup, make docker-up and make cli run the same checks themselves.


What it checks

Check A problem
Docker is installed Fails
The Docker daemon answers without sudo Fails, and tells a stopped daemon from a missing docker group
Docker Compose v2 (docker compose) is available Fails. The standalone docker-compose alone only warns
~/.gitconfig is a file with your name and email Warns
~/.ssh exists Warns. Without it the CLI clones over HTTPS with your forge token
The workspace .env As make env-check. A duplicate or malformed key, or an unreadable file, fails. The rest warns

make cli also checks the container. See make cli.


Before the first make setup

A missing .env is not a failure here. The pre-flight prints an info line and passes. Only make env-check fails on it.

  • .env not created yet (make setup creates it from .env.example)

See also


Back to top

splent. Distributed by an LGPL license v3. Contact us: drorganvidez@us.es