Deploy an app · App Platform
Deploy from a Git repository, your registry or a public image. Git repository: Build from a public GitHub or GitLab repository. Each push to the branch can…
Deploy from a Git repository, your registry or a public image.
Sources
Git repository: Build from a public GitHub or GitLab repository. Each push to the branch can redeploy.
Your container registry: Run an image from your ByteNests registry. Pushing a new image to the tag redeploys.
Public image: Run a public image from Docker Hub, GHCR or another registry. Pin a tag rather than latest.
Component types
Web service: An HTTP app or API. Gets a URL and HTTPS.
Static site: Built once and served as files. No server runs.
Worker: A background process with no public URL.
Job, before deploy: Runs once per deploy, for example database migrations. If it fails, the old version keeps serving.
Create the app
Open Apps and choose Create app.
Choose the source. For Git, enter the repository URL, branch and, for monorepos, the source directory.
Choose the type. For Git sources, leave the build and run commands empty and we detect them from your code, or set them yourself. Set the HTTP port; it is also passed to the app as PORT.
Pick a size and the number of instances. Two or more keep the app up during deploys and host failures.
Add environment variables. Mark secrets as Secret: they are encrypted and cannot be read back.
Optionally attach a managed database. The app gets its own database user, is let through the database firewall, and receives DATABASE_URL (REDIS_URL for Valkey).
Name the app and choose Create app.
The first deployment clones or pulls, builds, runs any pre-deploy job, checks health, then goes live. Billing starts when the first deployment goes live.