The other day I wrote a guest post over on the WP Tavern about using Laravel Forge to run WordPress in the cloud.
Laravel Forge now offers 1-click installs of WordPress on any cloud server. In the post I go through how to create a new server, provision it in a secure way, setting up a MySQL database, installing WordPress and installing a free SSL certificate. All made super easy by Forge.
Using Forge with WP Pusher
Forge and WP Pusher plays very well together. Use Forge to set up the server and install WordPress. Then use WP Pusher to install you plugins and themes from GitHub or Bitbucket. Forge will take care of keeping the server up to date with security releases and new SSL certificates, WordPress will take care of updating itself and WP Pusher will take care of updating plugins and themes when you commit and push a change.
If you have any questions about Forge, WordPress, Git or WP Pusher, don’t hesitate asking it here or send me an email.
Read the full article here.
Push-to-Deploy is the feature of WP Pusher that will keep your WordPress websites up-to-date every time you push some fresh code to your Git repositories. In this post, we are going to take a look at what Push-to-Deploy is, how best to use it for an effective workflow.
Last week I wrote a guest post over on the WP Tavern about how fundamental Git is for WordPress teams. In the post, I mention 3 signs that will make it obvious to me that your WordPress development team is not in fact working as a team – but rather as small 1-man teams. The 3 signs are:
- Lack of version control
- Lack of a code collaboration platform
- Lack of a deployment strategy
Git is a fundamental enabler of team work, so without it, it’s hard to get to step 2 and 3 in that list. If you want to read the article, check it out over on WP Tavern.
When you use Git in your WordPress deployment flow, there is a special configuration file you should be aware of.
.gitattributes can drastically clean up your plugins and themes for end users. Follow along and I will show you how simple it is to use.
This is the story about how I wasted 3 days, but also, which is more important, how I set up continuous integration for WP Pusher with CircleCi. With a continuous integration service, you can have your tests run on every commit and ensure that nothing is broken. That is, if you have some tests to run of course.
NB. The WP Pusher file is no longer supported in WP Pusher.
Composer seems to be something everyone is talking about in the WordPress community these days. It is a great tool for developer productivity and code reuse. However, if you are trying to use Composer to distribute your WordPress product to end users, you might be doing it wrong ™.
During the beta testing of WP Pusher, I have seen numerous examples as to how WordPress developers use Git to manage their projects. WP Pusher is opinionated in terms of how your Git setup needs to look, in order to use the service. In this post, I will try to explain why.
I think most people can agree that WordPress seen from a user perspective is pretty good. It’s easy for users to create and publish content, and plugins and themes can easily be installed from the official repositories. If you can use Microsoft Word, you can pretty much use WordPress.
The opposite is the case of the developer experience.