Deploy your first app

An app is one project: its services, its database, and its variables, domains and volumes. You can make one from the website or from your terminal, and the two work on the same app.

From the websiteCopy Anchor Link

1. Connect the repository. Sign in with GitHub, GitLab or Bitbucket and pick the repository, or paste its address.
2. Check the plan. Clusterz reads the repository and shows what it would make: the app, the folder it is built from, how it is built and started, the command that runs your migrations, and the database it needs. Anything it could not decide is asked as a question, one for each gap.
3. Create and deploy. One button makes the app, its database and its variables, builds it, runs the release command, and moves traffic to it. A step that fails leaves nothing half made, and says which step failed and why.

From your terminalCopy Anchor Link

Install cluz first, which the CLI page explains. Then, in your repository:

cluz login
cluz init            # writes clusterz.yaml from what Clusterz finds; check it and commit it
cluz up --wait       # makes or updates the app and deploys it

cluz up --dry-run shows what would be made and changes nothing. Without a clusterz.yaml, cluz up uses what Clusterz finds by reading the repository.

After the first deployCopy Anchor Link

Every push to the branch reads clusterz.yaml again, applies what changed in it, and deploys. This holds for GitHub, GitLab and Bitbucket, for apps made in the browser and for apps made from the terminal.

Your app has an address made from its name. Move it to your own domain when you are ready.

Where nextCopy Anchor Link

• The project file: everything clusterz.yaml takes.
• Deploy: builds, services, releases and rollback.
• Databases: add Postgres, with sign-in, storage and live updates.