WP Pusher 2.1.0 Has Landed

What’s new?

Tokens: Until now, in order to authenticate with GitHub, you had to manually create a token. For Bitbucket, which doesn’t offer API tokens, you had to enter a pair of valid user credentials. This release instead utilises OAuth to obtain the tokens, and it’s only 1 click!

This is possible because of a small service we built that uses OAuth to do the authentication. It’s not possible to do OAuth from a WordPress plugin, without shipping a secret token together with the code (which you do not want to do), so we built a small service, on our own server, that handles all the communication with GitHub and Bitbucket. We don’t store anything. Your GitHub and Bitbucket tokens are not stored on our servers.

This update makes Bitbucket authentication a lot safer, since you don’t need to type in your user credentials. So far, I’ve recommended setting up a dedicated Bitbucket user, with read-only credentials, but I know how tempting it is to just enter your own credentials (which are then stored in WordPress). This is all unnecessary now. Just click 1 button and obtain a token.

Push-to-Deploy is now set up automatically: Previously, enabling Push-to-Deploy required you to manually set up the webhook on GitHub or Bitbucket. This is now entirely handled by WP Pusher. Just tick the Push-to-Deploy checkbox, and WP Pusher will set up the webhook for you.

Manage your WP Pusher license: This service has actually been out for a while, but has never been officially announced. If you go to license.wppusher.com, you can manage your WP Pusher license from a central dashboard.

I’m really happy with the changes introduced in this release, and I’m excited to hear what you think about it!


Want to read more like this?

Add your email address below to stay in the loop when new content arrives. You'll never miss a post.

Peter Suhm

Peter is a web developer from the Land of the Danes. He is the creator of WP Pusher and a huge travel addict.