Publishing changes

Save and deploy a host's configuration, and choose the right deployment type.

Changing a host's configuration does not affect the running server until you publish it.

  • Save vs. publish - what each action does
  • Deployment types - choose the right publish mode
  • Preview what publishing will do - the On publish indicator
  • Following a deployment - track progress and review logs

Save vs. publish

  • Save stores your changes in TurboStack only. The server is unchanged, and an unpublished changes badge appears as a reminder.

  • Save & Publish stores your changes and deploys them so the server matches your configuration.

Deployment types

Open the Save & Publish menu (the ▾ next to the button) to choose how the configuration is applied:

Action What it does When to use
Save & Publish Applies your (unpublished) configuration changes to the server. Everyday changes.
Save & Full Publish Runs a complete deployment that re-applies the whole configuration. After larger changes, or to be thorough.
Save, Delete & Full Publish Full deployment that permanently removes anything you deleted from the configuration. Only when you intend to remove resources and their data.
The Save & Publish menu showing the deployment options
The Save & Publish menu showing the deployment options

Preview what publishing will do

Before you publish, TurboStack shows an On publish indicator in the host header and in the History view. It tells you the scope of the next publish, so there are no surprises:

On publish shows What it means
Nothing to publish The server already matches your saved configuration.
A list of components (for example nginx, php, mysql) Only these parts are redeployed, which is faster.
Full Deploy The whole configuration is re-applied.

TurboStack only escalates to a full deployment when a change is structural, such as adding a system user. Ordinary setting changes redeploy just the affected components. Changes that cancel each other out, or backup settings, do not trigger a deployment on their own.

Following a deployment

When you publish, a progress dialog tracks the deployment with a live spinner and the latest log output, refreshing automatically until the job finishes, errors, or times out. While a deployment is running, the publish and credentials actions are temporarily disabled to prevent overlapping deployments.

You can review every past deployment - including who triggered it, the result, and the full logs - on the Deploys tab of the History view.

© 2026 Hosted Power — TurboStack