What FLY8HT has actually run.

A three-app pnpm monorepo with a Postgres service and eight required environment variables.

What happened. FLY8HT found all three apps (a Next.js admin, a Node API and a Vite web app), let you pick one, read the declared pnpm version, detected Postgres from docker-compose.yml and listed every variable from .env.example.

What we fixed · Pre-filling a production build alongside a dev-only script produced a broken pipeline. The target picker now only pairs a build with a real start script.

A Java PDF toolkit with no JavaScript toolchain at all.

What happened. Pointed Dockerfile mode at docker/embedded/Dockerfile with container port 8080. FLY8HT ran the full multi-stage Gradle build (about ten minutes cold) and published the app on a local port.

What we fixed · Slow-starting apps can accept a TCP connection before their HTTP layer is ready. We documented this as a known gap rather than hiding it.

A private repository cloned through a connected GitHub account, then built inside Docker.

What happened. Cloned via GitHub Device Flow, built in a container, and served at localhost. In the Development tab, a dev command of npx vite --port $PORT gave a working, interactive live preview.

What we fixed · Two real bugs surfaced here: the wrong HTTP auth scheme for private clones, and the host's HOME leaking into containers. Both fixed and regression-tested.

The first project ever built inside a Docker container by FLY8HT.

What happened. yarn install ran inside a labelled, auto-removed container in about two seconds; the app answered on its assigned localhost port.

What we fixed · A miscategorized dependency crashed the very first container build. It was found and fixed, and the bundle got 1.8 MB smaller.

A Yarn 4 workspace whose apps depend on internal workspace:^ packages.

What happened. Install now runs from the workspace root and uses the exact pinned Yarn 4.6.0 via Corepack, so internal packages resolve instead of 404ing on the npm registry.

What we fixed · The example app's own build still needs environment variables it doesn't document, and FLY8HT reports that failure honestly.

A Java project whose web app lives deep in src/main/webapp.

What happened. Automatic detection now honestly says there's nothing to serve at the root. A manual start command of npx serve -l $PORT in the right directory runs it.

What we fixed · This repo is why FLY8HT stopped reporting success for a static server that 404s on every request.

A minimal Bun HTTP server, used to verify bun end to end.

What happened. Installed and started with bun, reached over HTTP, and stopped cleanly.

What we fixed · It hardcodes its own port, which exposed that the Port field in manual configuration was being silently ignored. Now it's honored.

The smallest possible Node server, and FLY8HT's everyday smoke test.

What happened. Paste, pick the branch, build, and Hello World! is served on localhost:3000. Used to verify retries, restarts and the branch picker.