flisk-up
Start a Flisk stack with `flisk up`, preview it first with `flisk up <stack> --dry-run`, and confirm the healthy URLs. Use when the user asks to run, start, or bring up their local services, or after
SKILL.md.claude/skills/flisk-up/SKILL.md
GitHubFlisk up
Start local services from service.json manifests. Flisk writes the Docker and Tilt configuration; do not write Dockerfiles, Tiltfiles, or routes by hand.
Workflow
- Run
flisk doctorif the machine has not been checked yet. Stop on unresolved errors. - Preview the stack:
flisk up <stack> --dry-run. Show the user which services and URLs will start. - Start it:
flisk up <stack>. Omit<stack>to start every stack. - Confirm health with
flisk status --json. Report each service's URL only after it reports healthy. - If
flisk uprefuses to start because generated files differ fromservice.json, regenerate from the source manifest. Use--ignore-driftonly when the user asks to start anyway.
Services that run without Docker
A service whose service.json declares command (for example "command": "node server.js", with appName, appType, port, dependsOn and an optional healthCheckPath) runs as a local process. When every selected service has one, flisk up needs no Docker and no Tilt: it starts them in dependsOn order, prints http://localhost:<port> for each, prefixes their output, and restarts a service that exits. It stays in the foreground; flisk down stops it from another terminal.
- Prefer
commandservices for a simple app (an API, a website, a worker). Use Docker services when the app needs a database, one gateway URL, or the container it deploys. - A database or cache can run in Docker next to
commandservices: give it animage(nocommand, nodockerfile) andflisk upstarts it withdocker run(a mixed run, docs/run-without-docker.md). Any other mix, such as a service built from a Dockerfile next to acommandservice, is refused withMIXED_RUNTIME. flisk up --jsonreports"runtime": "native"and each service's URL. Read output withflisk logs --service <name>.- Guide: docs/run-without-docker.md.
Guardrails
- Ask before starting a large stack or one likely to build many images; cold builds can take several minutes.
- Use
flisk up -fonly when the user agrees to kill the existing Tilt process. - Do not edit
.autogenerated/or other generated output. Changeservice.jsoninstead. - Flisk runs locally. Do not use it to deploy to a cluster.