Build and runtime configuration
Configure how Infralane builds your source and runs the application. Git and ZIP sources use build settings; a Docker image already contains its runtime and startup behavior.
Source directory and branch
For Git, choose the branch and application directory. Use / for the repository root, or a subdirectory such as /apps/web for a monorepo. For ZIP, / detects a single wrapper folder; you can instead name a directory inside the archive.
Choose a runtime
| Runtime | Use it for | Configuration |
|---|---|---|
| Node.js | JavaScript/TypeScript applications and frontend builds | Verify project build and start commands |
| Python | Python web services, workers and services | Verify dependency and process commands |
| Go | Go services and workers | Provide a start command; the form suggests go build -o app and ./app |
| Plain HTML/CSS/JS | Files that are already ready to serve | Choose a publish directory containing index.html; no build or start command |
Static sites use Node.js for a source build, or Plain HTML/CSS/JS for prebuilt files. Use amd64 servers for Git and ZIP builds. The MCP schema has a narrower runtime list than the dashboard.
Commands and ports
Build command is optional when a supported runtime automatic build script can prepare your project. Enter an explicit command when your project needs a particular build. Include dependency installation if your chosen workflow requires it.
Start command must launch the long-running process for a web service, worker or TCP/UDP service. Go and source-based TCP/UDP services require an explicit command. Static sites do not use one.
Container port must match the web application’s listener, between 1 and 65535. Bind the application to an interface reachable from outside its container process, commonly 0.0.0.0. Workers and TCP/UDP-only services do not use this HTTP port; configure service ports under networking.
Static-site publishing
Set Publish directory to the directory of final public files, relative to the source directory: for example dist, build, out or . for a plain site at the source root. It must contain index.html. Only those public files enter the static runtime image.
Enable Single-page app routing for browser routes that should return index.html. Missing assets still return 404. Keep it off for a site whose paths should resolve to actual files.
Resource allocation
Choose an active pool in the current project, then set positive CPU and memory limits. Application memory is entered in MB. Compare allocations with the server’s capacity and observed usage; configured limits are not measurements or a guarantee that all apps can peak simultaneously.
Environment variables
Add runtime key-value pairs such as APP_ENV and DATABASE_URL. Keep credentials in value fields, never names, URLs or commands.
During creation, Import .env file reads an environment or text file up to 1 MB in your browser. The file itself is not uploaded. Its parsed values become editable fields and are sent as application configuration when you deploy. Imports support comments, optional export, quoted and multiline values. Later duplicate keys win, existing matching rows are updated, and unrelated rows remain. Substitutions such as ${NAME} stay literal. Complete empty values before continuing.
Saved environment values are redacted when settings load. You can keep an unchanged saved value or replace it; you cannot reveal the original saved value. Reveal controls apply only to new values you enter. Renaming a saved variable requires a replacement value.
Review shows variable names without their secret values. After saving, replacement values are cleared from the form. Do not print values in logs or include them in screenshots and support messages.
Persistent data
Add a named volume with an absolute mount path and a positive size only when the application needs durable filesystem data. See Persistent volumes and backups for lifecycle and recovery details.
Review before deployment
Check the exact source, directory, commands, application type, port and allocation. Confirm required environment keys, volumes and public/private networking. Saving source, resource or runtime settings starts a deployment; saving only the description does not.