Deployments

Every push to your configured branch triggers a deployment. Risved clones the repo, detects the framework, builds a Docker image, starts a container, checks its health, and routes traffic, automatically.

Build pipeline

Each deployment goes through eight phases:

1. Clone, shallow git clone of the target branch
2. Detect, framework detection and Dockerfile generation
3. Build, Docker image build with layer caching
4. Start, container start with environment variables injected
5. Health, HTTP health check to confirm the app is responding
6. Route, Caddy reverse proxy configuration for the domain
7. Cutover, old container stopped with a 10-second grace period
8. Live, deployment marked as live

Build logs

Build output streams in real time to the dashboard. Logs are colour-coded by phase and retained for 30 days by default. You can change the retention period in settings.

Triggers

Deployments can be triggered by:

• A git push to the configured branch (via webhook)
• The deploy button in the dashboard
• The risved deploy CLI command

Zero-downtime

Risved uses a blue-green deployment strategy. The new container starts and passes health checks before the old one is stopped. Traffic switches over with no interruption.