Docs
Docs
homeport turns a repo, an example or a folder of files into a running app with an HTTPS address. These pages cover what it detects, what you can configure, and what it costs.
New here? Start with the Quickstart: most apps deploy with no configuration at all.
Start
- QuickstartConnect GitHub, paste a public repo URL, deploy an example or upload files, and get a live HTTPS address on homeport.run.
- What homeport detectsHow homeport reads your repo to pick a build: Go, Bun, Laravel on FrankenPHP, rsc-kit apps and static sites, and what it builds and runs for each.
- homeport.yaml referenceEvery key homeport.yaml accepts, with its type, its default and an example. Commit it only when detection needs overriding.
Configure
- Environment variables and secretsSet environment variables and secrets for an app, how they are stored, when they reach your build and your app, and the names homeport sets for you.
- Custom domainsAdd your own domain to a homeport app: the DNS records to create, how verification and TLS certificates work, and what happens with www.
- Sleeping, always-on and sizesHow homeport apps sleep when idle and wake on the next request, how to keep one always on, and the memory and CPU sizes each plan allows.
Deploy
- Deploy from your own CIBuild in GitHub Actions and deploy the result to homeport with the homeport-sh/deploy action, authenticated with OIDC and no stored secrets.
- Upload a siteDeploy a static site by uploading a zip or a folder: the size limits per plan, what an upload may not contain, and how to ship a new version.