MultiConnectMultiConnectDocs Website home
MultiConnectCloud › Website Deployments

8. Update your website

Upload a new build

  1. On the website page, press Update. The same five steps open, filled in with the current settings.
  2. Change any settings you want, then on the Build step choose Upload New Build and pick the new zip.
  3. Leave Rollback on failure on, so the previous build is restored if the new one fails.
  4. Press Submit.

The current build keeps serving until the new containers are healthy. The new build and any changed settings go live together.

Change settings only

Press Update, change the settings, and on the Build step choose Keep Current Build. Then press Submit.

You changed What happens
SPA fallback, Compression, Cache Max-Age, Basic auth or Build Output Directory Saved, and the current build is redeployed with the new settings
Only the name or autoscaling settings Saved. Nothing is redeployed
Anything, on a stopped website Saved. It applies when you start the website

When the current build is redeployed, Rollback on failure applies as it does for a new build: leave it on so the previous containers keep serving if the redeploy fails, or turn it off to leave a failed redeploy in place to inspect.

A changed Build Output Directory is checked against the current build, and refused if that build has no index.html there.

Change plan or regions

To change Press Then
The hosting plan Update in the Hosting Plan panel Choose a plan, keep Rollback on failure on, and press Update plan
Regions and containers Scale Change the regions, then press Apply scaling

A plan change is blue/green like a deploy. Before moving to a plan with a lower container limit, scale down to that limit.

Rolling back

Situation What happens
A new build or plan never becomes healthy, with Rollback on failure on The previous one is restored automatically. The operation shows Rolled back, and the site keeps serving the previous build
A new build is healthy but has a bug There is no button to go back. Upload the previous build again, as in "Upload a new build"

Keep your own copy of each build you might want to go back to, or tag your builds in source control so you can rebuild them.