This is follow up to my previous post about EasyEngine v4.
I have covered most pain areas last time. We were hoping to get a PHP based minimal release by July 2017 but we failed.
I do not have any ETA for v4 this time. It may happen next month, next year or I might give up on the project someday (unlikely).
Last time announcing an ETA created a lot of pressure on me and my team. So I am avoiding committing to a date for something we still consider a side project at rtCamp.
The only promise I can make is that if we abandon EasyEngine, I will be the first to let you know. Sorry but I do not like to sugar coat reality.
So walk along at your own risk!
What are we doing?
It has been 6 months since the last blog post and almost 14 months since last release.
The awesome performance you get with EasyEngine took more three years of research and tweaking to figure out all the magic hidden inside WordPress and Nginx.
This time we are attempting to make development workflow easy which needs a lot of research in a different area.
Still for better utilization of resources, we divided our already limited resources into two groups – research and development. We did not have dedicated research team before.
Research team's current primary focus area is exploring docker and possibility with containers at large. This group led by Mriyam studied many tools such as Dokku, Flynn, Swarm, Kubernetes, Deis, Helm, Mesos and more. In case you are just interested in the topic, this post covers a quick overview of these Docker tools.
We are still away from using any of these in production but we have explored enough to have confidence that docker is way forward!
The development team for next v4 needs to be an expert in PHP command line development.
As the v4 development cannot start before research team finalizes a docker (container) based architecture and other underpinnings, we asked them to contribute to the WP-CLI codebase.
One of them Siddharth contributed so much to the WP-CLI that he is now a core committer to that WP-CLI project.
So what’s next?
Since dev team cannot code unless docker and other architectural decisions are not finalized, the immediate goal is to get this docker-thing sorted.
Unfortunately, most docker usage in production is by big folks running multiple servers. We want to bring some of that power with a lot of simplicity to our favorite $5/month VPS.
The high availability and fault tolerance are not possible to achieve on a single machine, but we still want docker for its simplicity and portability. The goal this time is to make a WordPress developer's life easy and for that, it’s crucial to bridge the gap between local dev machine and the remote server. This is where docker makes sense to us!
So if you are a docker expert, we need you immediately. Of course, we need more helping hands by all means!