Environment Sync and Cache Management

Applies to: All

Overview

Sync copies content from one environment to another (for example staging → live). Clear caches refreshes stored page copies so visitors see your latest changes. These are everyday tools for Codeless teams promoting editor work to production.

Key concepts

  • Database — stores pages, menus, and configuration. Syncing the database copies editorial content.
  • Files — uploaded images and documents on the server. Sync files when editors added new media on staging.
  • Both — full content promotion; may take longer and use more credits.
  • Cache — saved HTML and data for speed. After theme or config changes, visitors may still see old pages until caches clear.
  • Varnish — FlexSite’s page cache layer; Clear caches refreshes it along with Drupal’s internal cache.

When to sync vs when to clear cache

SituationAction
Editors published new pages on stagingSync database (and files if media changed) to production
You changed theme or site settingsClear caches first; sync if changes were made on another environment
Developer deployed code on FlexLabUse Git deploy, not sync, for code — sync is for content

Prerequisites

  • Source and target environments ready.
  • Permission to sync on the target environment.
  • Credits for sync jobs; FlexSite may take a safety backup first.

Steps — sync environments

  1. Open the target environment Overview (the copy receiving content, often production).
  2. Click Sync Environment or Sync from Another Environment.
  3. Select the source (e.g. staging).
  4. Choose Database, Files, or Both.
  5. Confirm and wait for completion. Review the live site afterward.

Steps — clear caches

  1. On environment Overview, open the actions menu.
  2. Click Clear caches.
  3. Wait for Cache cleared successfully.
  4. Reload the public site in a private browser window to verify.

Restrictions

  • Cannot sync into an environment still provisioning.
  • FROZEN billing blocks sync until ACTIVE again.

FlexLab note

Developers deploy code through Git branches. Use sync when marketers moved content on staging and production needs the same pages — not when PHP or theme files changed in the repository.