The problem with having multiple website development environments is that sometimes it’s a hassle to keep them all up to date. You end up wasting your time on complicated flows, or worse – you start making changes on the live site. Luckily, your cowboy coding days are over, thanks to Local Sync.
Local Sync lets you quickly sync your local environment with staging and production ones. Want to deploy a website from your computer? No problem – just use Local Sync to push it to the website server. It also works the other way; you want to make changes to the live website without breaking it? Local Sync will push the latest version to your local environment, so you can get to work.
Here’s how it works:
Q: What’s the difference between the Clone feature and Local Sync?
A: Clone needs to create a snapshot first. This snapshot is transferred to AWS, and then cloned to destination website. This makes Clone an ideal tool to deploy a WordPress website – it’s more robust, but also slower and more resource intensive. Local Sync is more suitable to sync changes between two versions of the same website, since it’s faster and simpler.
Q: Why is Local Sync in beta?
A: There are so many different server configurations out there, it’s impossible to create unit tests for them. That’s why we need you to use it whenever you can, and send us feedback and bug reports. While we don’t expect that Local Sync would cause major issues, we still recommend using Clone for mission critical websites. Clone’s been battle tested and fine tuned these past 2 years.
Q: Will Local Sync be a premium addon after beta?
A: Yes. However, our goal is for Local Sync to be universally used, and it that sense you will not experience sticker shock. We are also considering bundling it with other premium addons, like we did with Backup and Clone. Stay tuned!
Q: What are your long term goals for Local Sync?
A: We are working toward two goals that will make your life easier:
By utilizing your browser as a tunnel, you are able to synchronize between your localhost website and other environments on the web. No desktop app or port forwarding needed.
Only new files and files that have changed are pushed to the destination website. This significantly reduces the transfer length and increases reliability
Database and files are being sent one by one, straight to the destination website
The database is overwritten during the sync
Yep, a hidden feature for those of you who read the whole thing! You can use Local Sync to quickly move a website from one server to another, without needing to wait for the backup to be created and sent to AWS.