Say Hi To WP Pusher 2.0.0

Today, version 2.0.0 was released. The main reason for the bump in versions from 1.1.8 to 2.0.0 was due to a few breaking changes that I felt was necessary to introduce. Please take a moment to read this post to stay up-to-date on what is new.

This version of WP Pusher includes 2 breaking changes:

  • Each plugin now has its own unique Push-to-Deploy URL (please see below).
  • The Pusherfile is no longer a part of WP Pusher. It’s main purpose was to allow people to use Composer, and I’m working on offering this functionality in an extension instead.

New stuff:

  • Updates can now be triggered from any place that can perform a POST request if Push-to-Deploy is enabled (please see below).
  • The UI and navigation has been improved.
  • Error messages has been improved and are now more accurate.
  • There’s a new extension offering push notifications in Slack.

The new UI in WP Pusher

Push-to-Deploy

The Push-to-Deploy feature is what makes WP Pusher awesome. It allows your plugins and themes to be automagically updated every time you push a change to GitHub, Bitbucket or GitLab. Recently, Bitbucket introduced some breaking changes to their web hooks, causing Push-to-Deploy to break for WP Pusher users. This forced me to figure out a way to make WP Pusher less vulnerable to these kinds of changes, that are completely out of my hands, in the future, and why I decided to completely redo the feature for version 2.0.0.

The change is a breaking change because every plugin and theme now has their own unique Push-to-Deploy URL. This means that you have to update all you web hooks to include this new URL. Having to do this sucks a little bit, but trust me: it’s worth it. This change has a very convenient side effect: Updates can now be triggered from literally any place that can perform a POST request to the Push-to-Deploy URL. This opens up a lot of new potential use-cases for WP Pusher users. For example, you can now update a plugin or theme directly from the command line:

# Updating a plugin from the command line with WP Pusher
$ curl -X POST http://blog.wppusher.com/?wppusher-hook=&token=12345&repo=12345

Pretty sweet, huh! But most importantly, WP Pusher is now a lot less vulnerable to breaking changes in GitHub, Bitbucket or GitLab.

Try WP Pusher

If you already have WP Pusher installed, an update notification will pop up in the admin. If you still haven’t tried WP Pusher, you can download it for free from here.

If you have any questions about the new changes, shoot me an e-mail.


Navigation