{"id":710,"date":"2016-06-15T23:48:00","date_gmt":"2016-06-15T18:48:00","guid":{"rendered":"https:\/\/thedevcouple.com\/?p=710"},"modified":"2017-07-17T09:16:48","modified_gmt":"2017-07-17T04:16:48","slug":"auto-sync-github-repositories-to-wordpress-with-wp-pusher-plugin","status":"publish","type":"post","link":"https:\/\/thedevcouple.com\/auto-sync-github-repositories-to-wordpress-with-wp-pusher-plugin\/","title":{"rendered":"Auto-Sync GitHub Repositories to WordPress with WP Pusher Plugin"},"content":{"rendered":"

With the right mix of minor to major functionalities, WordPress developers are building products for clients as well as for themselves. The most native procedure is, you develop a theme or a plugin locally and then host it somewhere. GitHub<\/a> is that somewhere<\/em> which has become a\u00a0popular choice for most professional developers over the years. The fact about Git being preferred despite the WordPress core still using\u00a0SVN<\/a> for version control tells all the pros that are associated with it.<\/p>\n

But let me remind you about a process which iterates each time you hand over the project to a client. I’m talking about the moving of project’s files onto the client’s server. The process is even more nerve-wracking when you have to do it manually via FTP. I’m sure you\u2019re doing it for most of the time, and you consider it worth repeating.<\/p>\n

WP Pusher Pugin<\/h2>\n

WordPress’ integration with third-party tools and software are taking this CMS to a next level and is not new. Unlike, several other such developments, there aren’t many tools which allow an easy integration of Git-managed themes and plugins with WordPress. In such a scenario, the existence of the WP Pushe<\/a>r plugin is quite a genius move.<\/p>\n

Peter Suhm<\/a>, the lead developer, describes the plugin functionality as:<\/p>\n

Pain-free deployment of WordPress themes and plugins directly from Git.<\/p><\/blockquote>\n

In other words, the WP Pusher plugin provides developers with one of the possible ways to\u00a0sync WordPress themes and plugins directly from GitHub, Bitbucket or GitLab to the client site. It is just another WordPress plugin which frees you from the hassle of\u00a0copying files over FTP\/SSH. So, in my opinion, it will be unjust if I don’t say that WP Pusher provides a captivating experience of Git with WordPress.<\/p>\n

Getting Started and Configuration<\/h2>\n

Unlike several other WordPress plugins, WP Pusher is not available in the repository. However, the free version can be downloaded from its website.\u00a0Once downloaded and installed, you can start managing all your GitHub hosted projects from one common place i.e. the dashboard<\/strong>.<\/p>\n

I am initially reviewing the free version, so the main settings page inquiring about the license and token details are not much of a concern. However, when one is dealing with private repositories, he’ll surely fill up these details by accessing the Pro version<\/a>.<\/p>\n

\"wp<\/p>\n

Next, click the sub-menus of “Install Plugin” & “Install Theme” and start adding your theme and plugin repositories instantly via the main menu for “WP Pusher”. The process involves the configuration of a few basic fields like\u00a0paths of your repositories (e.g. GitHub, BitBucket, or GitLab), links to plugin and theme’s branch or folder, etc. These simple options make\u00a0the plugin lightweight and easy to use.<\/p>\n

\"wp<\/p>\n

Push-to-Deploy<\/h2>\n

One of the key highlights of this plugin is its Push-to-Deploy<\/em> feature. The tiny miny, checkbox which appears on both the install plugin and theme page\u00a0automatically updates your project the very next moment you push your commits to GitHub. This means no fuss of updating and maintaining newer versions manually.<\/p>\n

\"push<\/p>\n

Procedure<\/h3>\n

The team behind this project developed it as an auto-updater in WordPress which gets synced and start working when you push your changes. Then a series of\u00a0rundown actions starts which begin\u00a0with a POST HTTP request sent via GitHub to the \u201cPush to Deploy URL\u201d. Next, GitHub webhooks assist WP Pusher in updating any plugin or theme repo. To create one such webhook, go to Settings > Webhooks & Services > Add Webhook. \u00a0Paste your Pust-To-Deploy URL here and save the settings.<\/p>\n

Wrapping it up!<\/h2>\n

Overall, the plugin seems to be great as it offers possibly the best auto-sync solution between GitHub and WordPress. So, there’s no point in troubling yourself with the manual handling of client’s files. I’ve tried it with a few plugin repositories, and everything worked perfectly well. WP Pusher is available at an affordable price ranging from $39 to $199.<\/p>\n

So, what are you waiting for? Grab a license for yourself and make a perfect addition to your developer’s plugin stack. Have you tried WP Pusher before? Share your experience and views about it. You can post below or reach me out through Twitter<\/a>.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

With the right mix of minor to major functionalities, WordPress developers are building products for clients as well as for themselves. The most native procedure is, you develop a theme or a plugin locally and then host it somewhere. GitHub is that somewhere which has become a\u00a0popular choice for most professional developers over the years. […]<\/p>\n","protected":false},"author":3,"featured_media":728,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":""},"categories":[18],"tags":[],"coauthors":[],"jetpack_featured_media_url":"https:\/\/thedevcouple.com\/wp-content\/uploads\/2016\/06\/WP-Pusher-WordPress.jpg","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/posts\/710"}],"collection":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/comments?post=710"}],"version-history":[{"count":0,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/posts\/710\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/media\/728"}],"wp:attachment":[{"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/media?parent=710"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/categories?post=710"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/tags?post=710"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/thedevcouple.com\/api\/wp\/v2\/coauthors?post=710"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}