From a Git repository to HTTPS with App Platform
Point App Platform at a repository and get a running app with a URL, a certificate, logs and one-click rollbacks.
Running a web app on a VM means looking after the OS, a reverse proxy, certificates and a deploy script as well as your code. App Platform takes all of that on. You bring a repository or a container image; it builds, runs and serves it over HTTPS.
Three ways in
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.
If your repository has a Dockerfile, it is used. Without one, Node.js and Python projects are detected and built automatically.
Only public repositories can be built for now. For private code, build the image yourself, push it to your container registry, and run it from there.
Create the app
Open Apps and choose Create app.
Enter the repository URL and branch. For a monorepo, set the folder the app lives in.
Choose the type: Web service for an HTTP app or API, Static site for files built once, Worker for a background process, or Job for something that runs before each deploy, such as migrations.
Set the port your app listens on. It is also passed to the app as PORT.
Pick a size and how many instances run. Two or more keep the app up during deploys.
Add environment variables, and mark secrets as Secret so they are encrypted and cannot be read back.
The first deployment clones the code, builds it, runs any pre-deploy job, checks that the app is healthy and then switches traffic to it. You can watch the build log live while it happens.
Add a database without copying passwords
In the create form, attach a managed database. The app gets its own database user, is let through the database firewall, and receives DATABASE_URL (or REDIS_URL for Valkey) as an environment variable. Deleting the app later removes only that user; the database and its data stay.
Deploy on push, roll back in a click
Turn on Deploy on push in the app settings and add the webhook URL and secret it shows to your GitHub or GitLab repository. From then on, every push to the branch builds and deploys.
If a release goes wrong, open Deployments, pick an earlier build and choose Roll back. A failing pre-deploy job also stops a release before it goes out, so the old version keeps serving.
Your own domain
On the app’s Domains tab, add a name such as shop.example.com and create the CNAME record it shows. The HTTPS certificate is issued automatically once DNS points at the app. If the domain is registered with ByteNests, you can add the record in the DNS editor.