Deploy from GitHub — Rumus Cloud

Connect a repository

The platform reads the repository contents to decide how to build. A Dockerfile is used exactly as written. Without one, the buildpack is chosen from the languages present.

Detected	Build	Start command default
Dockerfile	docker build	Image entrypoint
package.json	npm ci, then build script if present	npm start
composer.json	composer install --no-dev	php-fpm, path from public/
requirements.txt	pip install -r	gunicorn app:app
go.mod	go build	Resulting binary

Environment variables

Variables are stored encrypted per environment and injected when the container starts, so they are never part of the image. Marking one as a secret keeps it out of build logs and out of the interface after saving.

rumus env set billing-service/api DATABASE_URL=postgres://... --secret
rumus env list billing-service/api

Releases

A push to the connected branch starts a release. The new container must pass its health check before traffic moves; the previous one stays available.

Ten previous builds are retained per service
Rollback is a single action and takes effect within seconds
Concurrent pushes cancel the older release rather than queueing both
A failed health check aborts the release and leaves the old container serving

Health checks

By default the platform checks that the mapped port accepts a connection. An HTTP check is better when the application has a readiness endpoint:

rumus service update billing-service/api \
  --health-path /healthz \
  --health-interval 10s \
  --health-timeout 3s \
  --health-retries 5

A common mistake. A readiness endpoint that also checks dependencies makes releases fail whenever a dependency is briefly unavailable. Keep it to the process itself.