SnapNGo command line

Build modular systems from the terminal: scaffold a spine, add modules, generate compose and env, bring services up. Commands below are the intended day-one surface.

CLI INIT ADD UP HEALTH

Install

shell

# install (illustrative)
curl -fsSL https://stall.one/snapngo/install | sh

# or package manager when published
# npm i -g @snapngo/cli

Scaffold & run

shell · my-stack

snapngo init my-stack
cd my-stack

snapngo add auth
snapngo add gateway
snapngo add catalog

snapngo up
snapngo health_

Command map

Command	What it does
init	Create project spine: layout, defaults, base compose/env stubs
add <module>	Attach a module (service ± remote ± package surface)
up	Start the stack (compose or runtime equivalent)
down	Stop the stack
health	Hit health endpoints for declared services
list	Show installed modules and ports

What you get

Spine

Project layout + env defaults
Gateway + auth when added
Observability hooks

Modules

Declared ports and env keys
Optional MF remotes
Lifecycle scripts

Health check

shell

# typical local ports (reference)
curl -s http://localhost:3100/health
curl -s http://localhost:3101/health

# or
snapngo health

Module sketch

module.json

{
  "name": "catalog",
  "service": { "port": 3104, "health": "/health" },
  "env": ["MONGODB_URL", "AUTH_SERVICE_URL"],
  "remote": { "name": "catalog_remote", "port": 4180 },
  "dependsOn": ["gateway", "auth"]
}

Day-one bar

From empty directory to green health should be a short command sequence. Topology and cut lines live in the architecture note; module contracts live on the developer surface.