Transitioning Changes from Staging to Live: A Guide to Synced Modifications

The Staging to Live Site Sync feature in Staq offers seamless deployment of changes from staging to live environments. However, certain types of modifications made within the Staq Panel of the staging site do not automatically transfer to the live site upon synchronization.

Key Changes Not Synced Automatically:

Inside Staq Panel, if you’ve modified any of the following inside the staging site:

• Adding server Redirects
• Modifying WP Config File
• Adjusting PHP Configurations (e.g., PHP version, Max Execution Timeout, Memory Limit)
• CRON Manager entries
• NGINX Config changes
• Configuration changes to Redis Object Cache
• SMTP Mailer details

these changes will not automatically sync to production. See below the summary of changes you’re required to make to the production site.

Sync Process and Review

When initiating a sync from staging to live, users are guided through a 3-step process within the Staq UI. While the sync transfers most changes, modifications listed above are excluded. Instead, upon reaching the “Review & Finish” step, users are provided with a summary of changes that must be manually replicated on the live site. Below is an example of how configurations inside the Staq Panel of the staging site doesn’t match production. It then invites the user to go ahead and update the settings inside production:

Conclusion

It’s crucial for users to understand that certain configurations and settings made exclusively within the Staq Panel of the staging site do not automatically propagate to the live environment during synchronization. By being aware of these limitations, users can ensure consistency and accuracy between staging and live sites by manually applying necessary changes after syncing.