BWEZE builds your app from a GitHub repository and serves it over HTTPS on a bweze.app address. This guide covers the first deploy, the settings that decide how the app runs, and what each push does after that.
Connect the repo
In BWEZE Platform, open Deploy. For a public repo, paste its URL, such as https://github.com/you/app.
Private repos deploy through BWEZE’s GitHub app, which you connect once per workspace:
- Open Settings › Connect GitHub and install the BWEZE app on your account or organisation, granting it the repositories you want to deploy.
- Back on Deploy, switch to Private repo and pick one from the list.
BWEZE clones with a short-lived token scoped to that one repository, and never stores a GitHub password. It builds from the repository’s root directory: an app in a subfolder of a monorepo cannot be deployed yet.
How it builds
With Auto-detect, BWEZE builds the Dockerfile at the root of the repo if there is one. Otherwise Railpack detects the language and framework (Node, Python, Go, PHP, Ruby, Java, static sites and more) and builds an image for it. Static (HTML/JS) serves a plain site or single-page app on port 80, for web services only.
A build has 15 minutes, 1.5 GiB of memory and 4 GiB of disk.
Pick a service type
On the Configure step you choose what the repo runs as. The type is fixed once the service exists; to change it, create a new service from the same repo.
| Type | What it is | Reached at |
|---|---|---|
| Web service | An HTTP server, public over HTTPS | https://<name>-<id>.bweze.app and your custom domains |
| Private service | An HTTP server only your workspace’s other services can reach | http://app-<name>-<id> from those services |
| Background worker | A process that runs all the time and listens on no port | Nowhere: it reaches out, nothing reaches in |
| Cron job | A command run on a schedule; nothing runs between runs | Nowhere |
Cron jobs have their own guide.
Each service runs one instance with 0.5 CPU and 512 MiB of memory. Instance size and count cannot be changed yet, and there is no autoscaling. Memory is billed at 20 RWF per GiB-hour while the service runs, and CPU at 30 RWF per CPU-hour for what it uses (how billing works).
Port and commands
Web and private services listen on the port in PORT: 3000 unless you set another, 80 for a static site. Workers and cron jobs listen on none, and setting a port on one is refused with invalid_port.
Two commands are optional:
- The start command replaces the image’s own command (
CMD), for examplenode dist/server.js. - The pre-deploy command runs once on each new release before it goes live, for example
npm run migrate. If it fails, the deploy fails and the release that was live stays live. It is stopped after 30 minutes and cannot be cancelled.
Both run as /bin/sh -c "<command>" after the image’s ENTRYPOINT, with the service’s environment variables, so the image needs a shell. Set them under the service’s Settings, or from the CLI:
bweze services set <serviceId> --port 8080
bweze services set <serviceId> --start-command "node dist/server.js"
bweze services set <serviceId> --pre-deploy-command "npm run migrate"
They apply from the next deploy.
Environment variables
Add configuration as one KEY=VALUE per line: on the Deploy form under Environment variables, and later on the project’s Environment variables page.
STRIPE_SECRET_KEY=…
BWEZE_URL=https://acme-db-1a2b3c4d.bweze.app
Variables are available at build time and at runtime: a Dockerfile build sees them as build arguments, a Railpack build as build secrets. Each release freezes the variables it was built with, so Redeploy after editing.
A service can have at most 200 variables, and names starting with KUBERNETES_ or BWEZE_AGENT_ are reserved. If the app needs a database, give it a Postgres backend and put the backend’s URL and key here.
What a deploy does
BWEZE clones the exact commit, builds it and rolls it out; a web service is live within a few minutes. Each deploy moves through these states, and the dashboard shows each step’s time:
queued → building → pre_deploy → deploying → succeeded
pre_deploy happens only with a pre-deploy command. A deploy can also end as failed, cancelled, superseded (a newer push took its place) or rolled_back.
Instances are replaced one at a time, and an old one stops only once the new one accepts connections on its port (a worker, after 10 seconds), so a deploy has no downtime. A rollout that has not finished within 5 minutes is rolled back on its own, and the previous release keeps serving.
Every push ships
Once a repo is connected through the GitHub app, every push to the deployed branch builds and ships a new release. One build runs at a time per app, and a push that lands while an earlier build is still waiting replaces it. Redeploy rebuilds and ships the latest commit; Remove tears the app down completely.
Logs
Build logs stream live while a build runs, so a failed build shows why. Runtime logs show the service’s most recent output: the last 200 lines, or up to 2,000. Both are in the dashboard.
Roll back
Every release keeps its image, its settings and a snapshot of its environment variables. Roll back on any earlier deploy in the dashboard points the service at that release again at once, without rebuilding, and with that release’s variables.
A rollback does not run the pre-deploy command again, and a release whose pre-deploy command never succeeded cannot be rolled back to.
Pull request previews
Previews are not available yet. BWEZE can build a preview of each pull request at <name>-pr-<number>.bweze.app with preview-only variables, but they cannot be turned on for a project yet.
The full reference
Deploy from Git in the docs covers each step, Services has types, ports and commands, and Environment variables has how values are stored.