# Deploys, Rollback and Registry Logins

> Redeploy a Docker Compose App, roll back failed deploys, compare versions, automate deploys with Git push, and manage registry credentials.

Source: https://flywp.com/docs/site/docker-compose-apps/deploys/

Every change to a Docker Compose App goes live through a deploy. A deploy sends your current Compose file, environment variables, and resource limits to the server, starts your containers, and confirms they are healthy. The **Deploys** page lists every deploy and its outcome, newest first, 10 to a page. FlyWP keeps the five newest versions that passed.

## Redeploy the app

Trigger a redeploy to restart the app with your current settings, for example after an image update.

Click **Redeploy** at the top of any page of your app, then confirm. FlyWP makes the containers again with the images that run now. This isn't a new version, and your data stays.

To pull the newest image of each tag and deploy it as a new version, click **Update Images**.

![The Deployments list with the result of each deploy and its Details link](https://flywp.com/wp-content/uploads/2026/11/compose-deploys.png)

## Automatic rollback

Turn on **Roll back an unhealthy deploy** under **Automatic rollback**. After each deploy, FlyWP watches the app for the **Health window** you choose, from 1 to 30 minutes. The select only appears while the switch is on. If the app isn't healthy by the end of that window, FlyWP runs the previous version again. Data isn't rolled back.

The app is healthy when each service runs and passes its health check, and the main domain gives no server error, for 60 seconds in a row. A service that restarts 3 times isn't healthy. FlyWP never starts an app you stopped. Automatic rollback is also skipped on the Free plan, and while a clone or transfer is still waiting for its data.

## Roll back a deploy

To return manually to an earlier version:

1. Open your app and go to **Deploys**.
2. Open the deploy you want to return to.
3. Click **Roll back to version**, then confirm.

FlyWP automatically takes a safety backup before rolling back, so you can always restore your pre-rollback state from the **Backups** page.

## Compare versions

Click **Compare Versions** on the **Deploys** page to see what changed between two deploys. Use the **From** and **To** selects at the top of the card to choose the versions. The comparison shows what changed in your images, environment variables, resource limits and Compose file. For a GitHub app, it also links to the commits on GitHub with **Compare on GitHub**.

FlyWP never shows the value of an environment variable. A changed one reads **Value changed**. If the two versions are the same, the page says "These versions are identical."

## Deploy each push

Apps connected to a GitHub repository can automatically deploy whenever you push to their branch.

1. Open your app and go to **Configurations** → **Compose file**.
2. Find the repository card and turn on **Push to deploy**.

With **Push to deploy** enabled, every push to the branch triggers a deploy. If GitHub doesn't have the app's webhook yet, the card will let you know. Turn **Push to deploy** off whenever you prefer to deploy manually.

## Registry logins

**Registry logins** lists your team's saved credentials for image registries. Pulling an image from a private registry requires valid credentials for that registry.

By default, FlyWP uses your team's oldest accepted login for that registry. If you want to use a different login, or none, choose it for this app.

## Images and build cache

The **Images and build cache** section shows how much disk space your app's images use. Check this breakdown to see which images take up the most space before cleaning them up.
