Features Git Push KubernetesPricing Docs
Sign in →
Docs / Deploying Apps & Databases
Deploying Apps

Deploying Apps & Databases

Three ways to deploy on Rubuz: push from Git, run a Docker image, or create a database.

Rubuz gives you three ways to put something on your server: push from Git, run a Docker image, or create a database. Every app runs in its own rootless container, and every app gets a domain with TLS.

1. Git Push

The main way to deploy. Connect a repository and Rubuz builds and runs it on every push.

  1. Open your server in Rubuz and click Deploy App → From Git.
  2. Pick the repository and the branch to deploy (for example main).
  3. Rubuz builds the app on your server from the repository’s Dockerfile, or from its compose file if it has one. Monorepo? Point Rubuz at the folder the app lives in.
  4. Add your environment variables. If the repository has a .env.example, Rubuz lists the variables it names so you can fill them in. Secrets are stored encrypted.
  5. Click Deploy.

After that, every push to the branch redeploys the app automatically. The new version starts, passes its health check, and then takes traffic from the old one.

Example: a Node.js API with a Dockerfile that runs npm start on the port in PORT. Push to main, and a minute later the new build is live on api.example.com.

2. Docker Image

Already build images in CI? Run them directly.

  1. Click Deploy App → From Image.
  2. Enter the image reference, from Docker Hub (nginx:1.27), GitHub Container Registry (ghcr.io/your-org/api:latest), or a private registry.
  3. For a private image, add the registry credentials once. Rubuz stores them encrypted.
  4. Set the port the container listens on, add environment variables, and click Deploy.

To ship a new version, push a new tag and update the image in Rubuz.

3. Database

  1. Open your server and click Databases → Create Database.
  2. Choose an engine: PostgreSQL, MySQL, MariaDB, Valkey, and others.
  3. Rubuz generates a strong password and gives you the connection string to paste into your app’s environment variables.

Databases listen only on the server’s private network, never on the public internet. Backups are encrypted and sent to your own S3-compatible storage or Google Drive.

Health Monitoring & Restarts

Every app comes with health checks. If an app crashes or runs out of memory, Rubuz restarts it and alerts you by email or webhook.

Still have questions?
Can't find what you need in the docs? Our engineers are ready to help.
Contact Support