Deploy and monitor

What goes out with a deployment

Every setting you change is saved, but not applied yet. The project’s Changes to deploy bar counts what’s waiting, service by service. See details lists each change (“Set … to …”, variable added, domain added…).

Changes made by a plan join the same list. In Plans, the To deploy section groups them by project.

Deploy

Click Deploy, check the number of changes and the cluster, then confirm. The engine applies the changes one by one. Only what changed is restarted.

New services start using resources as soon as they run, within the cluster’s cap.

What blocks a deployment

• The project isn’t attached to a cluster: attach it first.
• Issues to fix: an empty required setting, two received variables with the same name… Each issue is flagged in its service, with Fix.
• Warnings: you can Deploy despite the warnings.

Automatic rollback

If a check fails during the deployment, Fransys undoes the changes: your last version stays online. The console shows Rolling back, then Deployment failed: rolled back, your last version stays online.

Open the service that’s struggling: its health checks and the latest lines of its logs tell you why it didn’t start. Fix it, then deploy again.

Undo changes before deploying

Undo changes puts each setting back to its previous value, then Fransys recalculates. Nothing is deployed. Some changes can’t be reverted automatically: the console lists them separately, to put back by hand.

Deployment history

The project’s Deployments tab lists the versions, newest first: Version N, its state, its duration and its operations.

State	What it means
In progress	The engine is applying the changes.
Succeeded	Everything is online.
Incident	An operation ran into a problem: open the version to see which one.
Failed	An operation failed; automatic rollback.

To undo a plan that has run or go back to a version of your code, see Rolling back.