Flisk changelog

version

1.4.53 → 1.4.56

version

1.4.52 → 1.4.53

version

1.4.49 → 1.4.52

version

1.4.48 → 1.4.49

version

1.4.47 → 1.4.48

version

1.4.45 → 1.4.47

version

1.4.44 → 1.4.45

version

1.4.43 → 1.4.44

version

1.4.42 → 1.4.43

version

1.4.40 → 1.4.42

version

1.4.39 → 1.4.40

version

1.4.33 → 1.4.39

https://raw.githubusercontent.com/flisk-sh/flisk/HEAD/AGENTS.md

− Flisk runs a local development inner loop for microservices and multi-agent systems on Docker and Tilt. It discovers services from manifests, generates necessary local configurations (Vite, TSConfig, Compose), and orchestrates live-reloading environments. It is designed for fast local development; it does not emit Kubernetes manifests by default and does not replace production cluster orchestrators like Helm, Kustomize, Flux, or Argo.− - Local-only by default: Do not add Deployment or cluster manifest generators without an agreed export scope. Keep cluster deployment policy with the user's Kubernetes workflow.− - Clean test artifacts before linting: Running tests with coverage creates `cli/test-results/` and `cli/coverage/`, which cause Biome checks to fail. Remove these directories before running `biome check .`.+ Flisk runs a local development inner loop for microservices and multi-agent systems. Services that declare a `command` run as local processes with no Docker; container stacks run on Docker and Tilt. It discovers services from manifests, generates necessary local configurations (Vite, TSConfig, Compose), and orchestrates live-reloading environments. It is designed for fast local development; it does not emit Kubernetes manifests by default and does not replace production cluster orchestrators lik+ - Local-only by default: Do not add Deployment or cluster manifest generators without an agreed export scope. Keep cluster deployment policy with the user's Kubernetes workflow. The one agreed export scope: `flisk export render`, `flisk export wrangler` and `flisk export compose` (opt-in) may generate `render.yaml`, `wrangler.toml` and a standalone `docker-compose.yml` (bring-your-own resources, runs without Flisk) from `service.json`. They write files only: they never deploy, never create DNS r+ - The one-command demo is P1: `npx @flisk-sh/flisk demo` is the first thing a new user runs, so a regression in it outranks every other task. Its CI suite is `tests/e2e/journeys/demo` (check "🎬 Demo command, run twice"). It runs the demo twice, because the second run meets the first run's Docker volumes, and runs it with Docker not running (cases N1-N3), where the demo must fall back to the two-service app as local processes (`cli/src/utils/native-demo.ts`, `cli/templates/demo-native/`). Native + - Clean test artifacts before linting: Running tests with coverage creates cli/test-results/ and cli/coverage/, which cause Biome checks to fail. Remove these directories before running `biome check .`.

https://flisk.sh/llms.txt

− Words that shape the stack: `postgres`, `worker`, `email`, `webhooks`, `redis`, `realtime`, `solidity`, `contract`, `indexer`, `agent`, `mcp`, `storefront`, `vue`, `react`, `svelte`, `python`, `go`, and `connected to <Platform>` for a third-party API. Install command if you mention one: `npm install -g @flisk-sh/flisk`. `flisk demo` is Flisk's own starter, not the personal demo.+ Words that shape the stack: `postgres`, `worker`, `email`, `webhooks`, `redis`, `realtime`, `solidity`, `contract`, `indexer`, `agent`, `mcp`, `storefront`, `vue`, `react`, `svelte`, `python`, `go`, and `connected to <Platform>` for a third-party API. Install command if you mention one: `npm install -g @flisk-sh/flisk` (`flisk demo` is Flisk's own starter, not the personal demo).+ - Not a developer (a musician, a designer, anyone who asked in plain words)? Call the JSON API with `plain=1`, `https://demo.flisk.sh/v1/demo?user=<handle>&q=<words>&plain=1`, and post its `reply` exactly. It says what they get in everyday words, with no Docker or Tilt. The demo is the same.+ - Who unfollowed an account: call `https://demo.flisk.sh/v1/unfollowers?user=<handle>&window=10m` (also `1h`, `1d`) and post its `reply`. X keeps no unfollow history, so `tracking_started` means no names yet, `partial` means "since I started watching", and `no_snapshots` means no data. Never list a name the API did not return.+ - MCP: `https://demo.flisk.sh/mcp` offers the tools `make_demo` and `get_unfollowers`. Add it with `claude mcp add --transport http flisk-demo https://demo.flisk.sh/mcp`.

version

1.4.13 → 1.4.33