News for hackers. Stuff that matters.

alexdykyi

fix(up): add Health checks section with /health URLs for test infrastructure; fix windows-binary script - #2481 #2481
Flisk: your whole stack, running locally with one command

Ask your AI agent for an app, or type four commands yourself. Flisk sets up the containers, database, routing, and secrets, wires them together, and keeps them in sync as you change things.

Re:Kimi K3.1 Pro and K3.1 Pro Highspeed on Friday October 23, 2026 @08:40PM (#50217261)
kimik2.5 flash was the game changer
Re:Docker Is Weird on Friday October 23, 2026 @08:34PM (#50217216)
which part of Docker feels weird to you, the image or the file that describes it?
Oh man now i see why its repo of the day https://news.ycombinator.com/item?id=50187746
thanks for sharing its made my day https://flisk.sh
I build magic tool. Its fascinating. Why? Because I decoupled it from real enterprise application. Have for you though about running one command that spins whole Tech stack?

Define each app once, then run flisk up

npx @flisk-sh/flisk demo thats it!
how do you run your stack? I bet you not have just one command:)
Really wanna hear your feedback
npx @flisk-sh/flisk demo

Flisk Cloning template: demo

The demo stack: restaurant ops with reservations, kitchen and floor control

Source: https://github.com/flisk-sh/flisk-restaurant-example.git Destination: /Users/myusr/.flisk/flisk-demo

Cloning into '/Users/myusr/.flisk/flisk-demo'... remote: Enumerating objects: 644, done.

remote: Counting objects: 100% (16/16), done.

remote: Compressing objects: 100% (15/15), done.

remote: Total 644 (delta 0), reused 2 (delta 0), pack-reused 628 (from 1)

Receiving objects: 100% (644/644), 221.44 KiB | 1.56 MiB/s, done.

Resolving deltas: 100% (353/353), done.

Cloned "demo" into /Users/myusr/.flisk/flisk-demo/

Next steps: 1. cd /Users/myusr/.flisk/flisk-demo 2. flisk doctor # check Docker/Tilt are ready 3. flisk up # start the stack

Runtime readiness: Docker and Tilt are only needed to start the stack: start them, then run `flisk doctor` (readiness) and `flisk up`.

Starting the stack in /Users/myusr/.flisk/flisk-demo...

Added VERDACCIO_URL_DOCKER, VERDACCIO_URL, TILT_ENV, DATABASE_URL, DB_PASSWORD, JWT_SECRET to .env (generated; existing values unchanged)

No generated Tiltfile yet; generating .flisk/.flisk-out/ ...

Generated: .flisk/.flisk-out/TILT_TECH_STACK.star

Generated: .flisk/.flisk-out/TILT_RESOURCE_DEFAULTS.star Generated: .flisk/.flisk-out/spec.master Generated: .flisk/.flisk-out/Tiltfile

Generated: .flisk/.flisk-out/.tiltignore Generated: services/platform/database-management/docker-compose.yml Copied: shared-platform-engineering/docker-templates → project root

Vendored Flisk extension → .flisk/.flisk-out/flisk-cli-ext/

To start Tilt: flisk up

Starting 6 services from all stacks (3 stacks, 6 services)... - reservation-api - reservation-app - kitchen-api - kitchen-worker - floor-app - menu-api

Frontend URLs: - reservation-app: http://app.flisk-restaurant-example.localhost:8081/reservati... - floor-app: http://app.flisk-restaurant-example.localhost:8081/floor-app...

Backend API URLs: - reservation-api: http://api.flisk-restaurant-example.localhost:8081/api/reser...

Opening the first frontend of flisk-restaurant-example - reservation-app: http://app.flisk-restaurant-example.localhost:8081/reservati... - floor-app: http://app.flisk-restaurant-example.localhost:8081/floor-app - kitchen-api: http://api.flisk-restaurant-example.localhost:8081/api/kitch... - menu-api: http://api.flisk-restaurant-example.localhost:8081/api/menu/...

Host ports: HTTP 8081, HTTPS 443, Postgres 15432 HTTP: wanted 80, using 8081 (selected from fallback range 8080-8180). To force 80: HTTP_PORT=80 flisk up

Postgres: wanted 5432, using 15432 (selected from fallback range 15432-15532). To force 5432: POSTGRES_PORT=5432 flisk up Override with HTTP_PORT, HTTPS_PORT, or POSTGRES_PORT.

Running tilt up... Using Tiltfile: .flisk/.flisk-out/Tiltfile

Tilt started on http://localhost:10350/ v0.37.4, built 2026-06-16

Re: on Tuesday October 20, 2026 @05:37PM (#50173038)
Do you know vibe coding?

Before you answer, please open 20 PRs with AI, get burned at least once, and only then come back.

Please share this with friends who just discovered Cursor / Claude / Grok.

¯\(ツ)/¯

This is a collection of things that happen when you vibe code that may not be well recognized, especially to beginners.

Disclaimer: Some of these are simply to demonstrate the quirky parts of AI-assisted coding and by no means encourage best practices.

Re:Faster Python startup with lazy imports on Friday October 09, 2026 @08:08AM (#50019347)
```

  +--------------------------------------------------+
  |  TDK CLI                                         |
  |  one service.json  ->  tdk up                    |
  |  local Docker + Tilt, no Kubernetes on the laptop|
  +--------------------------------------------------+

        service.json
             |
             v
     +------------------+
     | tdk up           |
     +------------------+
        |    |    |
        v    v    v
     Dockerfile  Tilt  Traefik / proxy
     nginx conf  env   generated client

  [ service.json ] --you own this
  [ .autogenerated/ ] --TDK writes this
  [ helm / argo / kustomize ] --still yours for prod
```

This is a local-dev contract, not another deploy tool: one `service.json` per service, then `tdk up` generates the Docker + Tilt loop (Dockerfiles, nginx, env, Vite/TS config, API client) and brings the stack up on plain Docker. Production stays with Helm / Argo CD / Kustomize.

The interesting bit is the boundary. You keep the manifest; the runtime files are generated and can be drift-checked. `tdk doctor` covers local readiness, and a `smoke` block can hit the public URL after `tdk up` so a green container is not mistaken for a working route.

Repo: https://github.com/tdk-landscape/tdk-cli-core

Install path they document: `curl -fsSL https://tdk-landscape.github.io/install.sh | sh` then `tdk doctor` / `tdk up`. Core CLI is MIT, no key required.