Manually configuring a project

FLY8HT’s automatic detection covers most real-world projects, but it’s deliberately honest about the cases it genuinely can’t guess safely, and routes you to a short wizard instead of a wrong assumption.

When this actually shows up

• A monorepo with more than one runnable application, where you pick which one.
• More than one lockfile present (npm and yarn both committed, for example). FLY8HT won’t silently guess which one is real.
• A framework it recognizes but doesn’t yet run automatically.
• A project you want to run differently than it was auto-detected.

The wizard

Steps adapt to what’s actually relevant. A “Target” step only appears for a real monorepo choice. From there: package manager, then build & run commands, then a review step before saving. A project that already has a saved configuration opens straight on Review, fully pre-filled, so tweaking one command doesn’t mean clicking through steps you don’t need.

Two build modes

Commands: a package manager plus install/build/start commands (the common case). Use this project’s Dockerfile: if the repository ships its own Dockerfile, FLY8HT builds and runs that image directly instead, no commands needed.

The $PORT token

Some tools (a static-file server like serve, for instance) can’t read the port from the environment; they need it written literally on the command line. Write $PORT anywhere in your start or dev command and FLY8HT substitutes the real port it assigned, so the command and FLY8HT’s own bookkeeping can never disagree.