Sometimes you need to quickly revert a change to your installation without waiting for a full build cycle of pushing a new commit. When you have a previous deployment you wish to make live again, Ryvn lets you quickly roll back to that deployment.

Rolling Back a Deployment

To roll back a deployment:

1

Navigate to Environments

Go to the Environments tab in the Ryvn Dashboard
2

Select Environment

Choose the environment containing your installation
3

Select Installation

Click on the installation you want to roll back
4

Access Activity Tab

Navigate to the Activity tab
5

Initiate Rollback

  1. Find the successful deployment you want to roll back to 2. Click the Rollback button next to that deployment
  2. Confirm the rollback in the dialog
Only successful deployments can be rolled back to. Failed deployments won’t appear as rollback options.

What Gets Rolled Back

The following configuration items are included in a rollback:

ConfigurationRolled Back?Details
Run CommandCommand used to start your application
Health Check PathPath and configuration for health checks
Docker CommandCommands for Docker-based deployments
Build AssetsBuilt artifacts from the deployment
Number of ReplicasScaling configuration from the deployment
Environment VariablesCustom environment variables

Persistent storage volumes are stateful between deployments and cannot be rolled back. Make sure your application can handle any data schema changes when rolling back.

Build Retention

Ryvn retains rollback capability for your most recent deployments. The number of previous builds available for rollback depends on your plan.

Automatic Deployments

If automatic deployments are enabled for your installation, rolling back will automatically disable auto-deploy. You can re-enable auto-deploy in your installation’s Settings tab after the rollback.

After Rolling Back

Monitor your application through the Ryvn Dashboard to ensure:

  • The rollback completed successfully
  • Your application is running as expected
  • All health checks are passing

For registry-based deployments, Ryvn will use the specific image and digest from the previous deployment. If that image is no longer available in your registry, the rollback will fail.