Urgent.News

What's breaking now, across thousands of outlets.

Thursday, 22 October 2026 Reading Room

Tech

Flisk.sh 101: One service.json, Then a Health URL

Part 4 of Goose lang and Flisk.sh 101. Use the Go backend. Do not pass --language goose . Flisk turns service.json into a local Docker and Tilt stack. You own the manifest. The CLI owns .autogenerated/ , including the Dockerfiles it writes beside the service. Editing those to "add Goose" is how the next flisk up deletes your work. Install Node.js 22.12 or newer. node -v npm install -g…

dev.to ·

Flisk.sh is a service creation tool that converts a service.json file into a Docker and Tilt stack. It requires Node.js 22.12 or newer. To install Flisk, run "npm install -g @flisk-sh/flisk". Flisk can be configured via environment variables such as TDK_HTTP_PORT, TDK_HTTPS_PORT, TDK_POSTGRES_PORT, and TDK_BIND_ADDRESS. Docker and Tilt are required to start a stack but are not necessary for a dry run.

To start a project and create a service, run "flisk project --yes", then "flisk resource --help", "flisk resource <resource-name> --type backend --language go --stack <stack-name>". The --language go option is chosen for this tutorial because the generated process is a long-running HTTP server. If --language go is omitted, the default is Bun and Hono.

The command "flisk doctor --no-ping" checks the Flisk installation, "flisk config verify" verifies the configuration, and "flisk up <stack-name> --dry-run" prints the services and health URLs without starting anything. The health URL is where the live URL checks can be accessed. Ports can be customized, and Dev ports bind to 127.0.0.1 unless TDK_BIND_ADDRESS is set.

After the first boot, Tilt is the inner loop. Flisk up <stack-name> starts the stack, and there is no local Kubernetes cluster in this tutorial. To stop the stack, use the command listed with "flisk up <stack-name> --help". Files such as service.json, Go source files, .autogenerated/ Dockerfiles, and hello.goose and total.goose can be edited. Flisk doctor also checks if backends have a /health route, and if not, it can be added manually.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Goose Lang 101: One Array, One Slice, One Function

Part 3 of Goose lang and Flisk.sh 101. Stay in ~/src/goose-flisk-101 . Run every file with goose file.goose before you build it. Goose has no heap allocator and no garbage collector.

  • Goose language uses grow-only arrays T[..] with valid references across push operations
  • Goose arrays are slices with reference and count, accessed via ^k for end-based counting

·dev.to

Goose Lang 101: Install the Compiler and Print One Line

Part 2 of Goose lang and Flisk.sh 101. The Flisk CLI stays closed. Goose is a whole-program compiler. It writes one C file and can run that C inside its own process through TinyCC.

  • Download prebuilt Goose compiler from releases page and place on PATH
  • Run "goose hello.goose" to execute code with print function
  • Use "goose build -o filename" to create binary with custom name

·dev.to

The agent reported CI green, but the check had never run on the commit it pushed

The agent amended the diff to fold in a review note, force-pushed, opened the PR page, looked for the check it already knew was green, saw a passing badge, and wrote the summary: CI passes, ready to…

  • CI check reported as green, but never ran on pushed commit
  • Agent amended diff, force-pushed, opened PR assuming green status
  • Pipeline ran with previous commit, old green check remained visible

·dev.to

Goose Lang and Flisk.sh 101: Same Repo, Different Processes

Part 5 of Goose lang and Flisk.sh 101. This is the join, and the join is a boundary. ./total is a Goose program. It prints and exits. The orders-api container is a Go process Flisk generated.

  • Goose Lang tutorial integrates with Flisk.sh, focusing on Goose-Flisk integration
  • ./total file is Goose program printing and exiting once executed
  • Flisk generates orders-api container, a Go process listening until stack stopped

·dev.to

Every Tool Parameter Is a Question Your Voice Agent Has to Ask

If you have ever designed a REST endpoint, you already know most of what it takes to give a voice agent tools. Name it well, keep the parameters tight, validate inputs, return something useful.

  • Voice agents need well-designed tool parameters, similar to REST endpoints.
  • Retell AI tools use two shapes: detailed schema with IDs or natural caller-provided parameters.
  • Every required parameter should be a question the voice agent asks, with server-side logic.

·dev.to

More from Thursday 22 October →