From that point on, every change you make, no matter how small, will be recorded by VersionPress and stored in Git.Īccessing the VersionPress page will show you a list of activity on your site, from all users, and give you a brief summary of actions (changed post name, deleted page, etc.).
After you install it, it proceeds through a build step which will connect your database and file system to a Git repository, and then start tracking changes immediately. VersionPress installs like any other plugin. I’m happy to say the product is certainly impressive, and addresses a problem I still haven’t seen anybody solve. If you have any interest in combining WordPress development and proper version control, I encourage you to check out their page and donate a few bucks to the effort.įortunately, Borek gave me a bit of a sneak peek of VersionPress so I can see how it works. The VersionPress team is looking to crowdfund the development of the plugin.
And since Git keeps things fairly compact, your version control files will never be all that large. This allows the plugin to track every change that’s made, and easily undo or revert back to any point. VersionPress approaches the problem by storing both your database and files in a Git repository. That’s why developers Borek Bernard and Jan Voráček began work on VersionPress, a version control system for WordPress. But managing databases, theme files and plugin settings across distributed teams is still a challenge. As the complexities of web development have increased, version control has become ubiquitous on both the front end and the back.
Rinse and repeat until you’ve got all your sites back.As much as version control has been an integral part of the core development of WordPress for quite some time, it has never been easy to integrate proper version control into the platform. The result should be a functional site in Local.
Here’s how to do it in Local Beta 5.1.1 (and maybe the production release of Local, too, but I haven’t tried it): You’ve got a new workstation and you’ve reinstalled Local, but now you need to reimport all your sites. All you need to do is to compress the folder of the site you want to import and then use Local’s import function.įor example, suppose that your workstation has failed unexpectedly and all you have are backups of your site folders. In MacOS and Local Beta 5.1.1, it’s easy to import an existing site. Just a clarification on my previous post: