☰

Getting Started

Deployment Deployment - Diagnose Migrations Staging

Site Management

Backups Client Reporting Passwords Plugin Automation Plugin Management - Global Plugins & Themes - Diagnose Plugins & Themes - General Plugins & Themes - Git Plugins & Themes - Logs Must Install White Label WordPress Updates

Caching & Performance

Caching Caching - Blogs/Articles Caching - Diagnose Caching - Git Caching - WooCommerce Redis Optimize & Scale

Security

Security Security - Firewall

SMTP, CDN & DNS

SMTP SendGrid CDN CDN - AWS CDN - Cloudflare CDN - Diagnose Domains & DNS

Server & Tools

Analytics & Logs CRON Jobs Database Debug Tool Git Monitoring PHP Settings Redirects SEO Tools Server Errors sFTP SSL

Staq Billing

Staq Billing > Account Staq Billing > Client Staq Billing > Setup

Media

Media Media - Diagnose Media - Optimize

Accounts & Billing

Accounts & Billing

General

WordPress Hosting Website Diagnose Troubleshoot - Other

How to sync a staging site to production


On this page

    You can push changes from a staging website to the live website without copying the whole site. Choose the database, plugins, themes, and content. You can also include or exclude specific database tables. Staq backs up both websites before it writes anything. PHP, redirects, and the other Staq settings are not copied. These steps select the data, run the sync, and show what you still update on the live website.

    Open the staging website

    1. Open the staging website.
    2. The environment switcher says Staging Environment.
    3. Click Sync Staging. You can also open Files and click Sync Staging in the rail.

    Sync Staging on the staging website

    Choose what to copy

    1. Step 1 is Select Data.
    2. Backups are created for the live website and the staging website before the sync starts.
    3. If you have more than one staging website, confirm the name on the page is the one you mean to sync.
    4. Complete Website copies the database, plugins, content, and themes.
    5. Select Types lets you choose which parts to push.

    Complete Website and Select Types

    Select the parts to sync

    1. Click Select Types.
    2. Tick Database, Content, Plugins, Themes, or any mix.
    3. WordPress setting changes use Database.
    4. Plugin or theme updates use Plugins and Themes.
    5. New files and images use Content. Add Database when those changes are stored in the database.

    Database, content, plugins, and themes

    Include or exclude database tables

    1. With Database ticked, open Scope.
    2. All tables copies every table.
    3. Include selected tables copies only the tables you name.
    4. Exclude selected tables copies every table except the ones you name.

    All tables, include selected tables, or exclude selected tables

    Leave live rows in place

    1. Choose Exclude selected tables when the live website has newer rows you must keep, such as form submissions or WooCommerce orders.
    2. Add those table names.
    3. Leave Content, Plugins, and Themes unticked if this sync is the database only.
    4. If you cannot exclude those tables, export the live data first and import it again after the sync.

    Exclude selected database tables

    Sync plugins and themes with those tables left out

    1. Keep the same table exclusion.
    2. Tick Plugins and Themes when those updates should go to the live website too.
    3. Click Sync Now only when the selection is what you want on the live website.

    Plugins and themes selected with tables excluded

    Watch the sync

    1. The page moves to Sync Progress.
    2. The event log creates a backup of the live website and a backup of the staging website before it changes the live website.
    3. Wait until the log says the staging site synced successfully.
    4. Click Review.

    Sync Progress backs up both websites first

    Update settings the sync leaves behind

    1. Review & Finish lists Nginx, PHP, Object Cache, Cron Jobs, WP Config, and URL Redirects.
    2. The sync does not copy these Staq settings. Match means they already agree. Needs update means you change that setting on the live website yourself.
    3. PHP can show a different max post size. URL redirects can exist only on staging.
    4. Click Go to Live Website and update each row that says Needs update.

    Settings the sync does not copy

    FAQ

    Do I need to take a backup first?

    No. Staq backs up the live website and the staging website before the sync. Restore either copy from Backups if you need it.

    Can I keep new orders or form entries on the live website?

    Yes. Exclude those tables, or leave Database unticked. If you cannot exclude them, export the live data first and import it again after the sync.

    Does the sync cost extra?

    There is no separate charge. Storage and bandwidth from the staging website count toward the live website’s usage.

    Can I have more than one staging website?

    Yes. Each one can have its own label. The sync page names the staging website you are about to push. Confirm it before you click Sync Now.

    Do staging and live use the same resources?

    Yes. Even though they are completely different environments, we apply the same resources to the staging environment just like the production website. Staging cannot use more PHP workers than the live website. Raise the workers on the live website first if staging needs more.

    What stays off on a staging website?

    You cannot configure both Cloudflare and CloudFront. WebP images are not served from the staging website either.

    I do not see Sync Staging

    You are on Dev or Live. Open the staging website from the environment switcher.

    Need some help?

    Open a support ticket if the control is not in Staq, or the change does not save.

    Need some help?

    We all do sometimes. Please reach out to our support team by dropping us a support ticket. We will respond fast.