Deploy Behavior

Git Web Manager

Understand how GWM applies updates and preserves changes.

Containers Health Checks

Standard Deploy

Standard deploys pull the latest commit, sync files, and preserve local changes. If Git detects uncommitted work, it will automatically stash and restore tracked changes after updating.

Permissions & Staged Installs

When dependency directories are not writable, GWM runs Fix Permissions and retries. If permissions still block dependency installs, it falls back to staged installs and swaps the result into place.

Staged Deployment Checks

When enabled, Git Web Manager performs builds/tests in a temporary staging directory before updating the live project.

  • Prevents failed builds/tests from touching production files.
  • Uses a git worktree under storage/app/deploy-staging.
  • Disable by setting GWM_DEPLOY_STAGING_ENABLED=false.

Force Deploy

Force deploy discards local changes and replaces files from the repository. Use for recovery scenarios or when you intentionally want a clean sync.

Undo Last Deploy

Use the Undo Last Deploy button to roll back to the most recent successful deploy. The button only appears when a rollback target exists.

Auto Rollback on Health Failure

If a deploy fails and the health check flips from OK to failing, GWM automatically attempts a rollback to the last known-good deployment.

Excluded Paths

Files listed in the project’s Exclude Paths are restored after deploy. Use this for uploads, caches, or host-specific configuration.

Whitelist Paths

Whitelist Paths restrict synchronization to only the listed files/directories. This is useful for partial deploy targets.

  • If Whitelist Paths is empty, all files are eligible.
  • Exclude Paths still apply even when a whitelist is configured.
  • For FTPS deploys, whitelist + exclude filters are evaluated before upload, so filtered files are never sent.