That’s interesting to hear. I too used to build sites from scratch, but over time the no of the site that I managed increased; right now; I delete and build production sites on while; rather than staging and all; I can test a lot of things, and EE server the instant deploy purpose.
The features which you mentioned; wish they were in EE too. :3
Thanks for giving us information regarding this, appreciate it. I know some people who can contribute to the project, will ask them if they can give in a hand in their holidays.
I can’t express how sad I feel to hear EE4 will be Docker based. 
Probably I’m going to give up EE because of this.
@portofacil May I know in details why you don’t like docker?
The way we are planning to use it, it will be invisible to normal users.
Docker “incapsulates” everything, and it is a pain in the *** to interact with the containers. Also, it creates a lot of complexity, including fake network interfaces in several cases.
I spent the last three years developing a miriad of support scripts to EE, written a GUI for my customers; these scripts all rely on WP-CLI and EE commands to perform their tasks, including automatic plugin installation and setup beyond EE native capabilities.
Also, it is common that an EE server runs dozens of domains (my largest customer has 4 VPSs with ~350 WPs each), and I’m really scared about what Docker would do in such case.
I’ve said this several times before, but in such case repetition is worth: instead of a “new” EE I’d rather have up to date packages for Nginx, REDIS and so on. We don’t need extra command line options as much as we need updated components to existing EE.
Same here ! [quote=“portofacil, post:25, topic:9809”] Instead of a “new” EE I’d rather have up to date packages for Nginx, REDIS and so on [/quote]
I would really prefer that.
Agreed 100%
Is it serious you are planning to use one container with the entire stack (Nginx, PHP, MariaDB, REDIS) per domain on each server?
I have published a detailed blog post about docker here https://easyengine.io/blog/how-we-plan-to-use-docker-in-easyengine-v4/
Some of you may like to jump to - https://github.com/EasyEngine/easyengine/issues/945
Nope. Please check my links above.
You may also check this https://github.com/easyengine/docker-compose-wordpress
I have just posted list of Nginx Modules present in custom build used by EasyEngine - https://github.com/EasyEngine/nginx-build/wiki/Nginx-Modules-List
Also, you can join @virtubox in http://easyengine.slack.com/ in #packages channel. They are working on updating Nginx build.
You can invite yourself to Slack from http://slack.easyengine.io/
I’m running tests to compare performance between Dockerize WordPress and local WordPress.
But for Nginx, the easiest is maybe to build it from source. There are some very good example like https://github.com/Angristan/nginx-autoinstall And my current script for nginx-ee is available here : https://github.com/VirtuBox/nginx-ee/blob/master/nginx-build.sh
I haven’t test yet the time needed to compile nginx on a $5 droplet, but on my vps it take less than 3 minutes.
Because if I have managed to run wordpress with Docker following Howtoforge tutorial, nginx container doesn’t include any additional modules. And
At the moment on Ubuntu 16.04 LTS, I have a working nginx 1.13.7 built from source with TLS 1.3 support. And Ubuntu repositories provide php7.0, 7.1 and 7.2 and Redis v4.0. MariaDB 10.2 is also available with the official mariadb repository.
Compilation can fail on a user system. That was the main reason to build packages. Apart from of source saving time!
Your script seems nice - https://github.com/VirtuBox/nginx-ee/blob/master/nginx-build.sh
If possible, get it working on https://build.opensuse.org/
Re: Docker performance test
You may post your finding on https://github.com/EasyEngine/easyengine/issues/945
I had issues when I have tried to build packages, but I will talk about that with mbtamuli on slack.
I will post all my results on github as soon as I have enough informations.
I was just about to start a thread like this after reading Rahul’s previous post, but since the thing is here i will avoid redundancy. Also the biggest heads (say it as you like) around this community are here!
Short way: We must contribute if we need the EE.
There are 2-3 very clear facts here.
1) EE has worked for us, it’s fast, it’s simple, it’s free and it’s community based (people helped me around here, in slack, etc… @virtubox, @portofacil, @rahul286 ).
2) EE needs to get further, new distros will come up like new Ubuntu, new ways are getting on like docker technology. Kubernetes is the new trend and everything is going under a central orchestration theory.
3) Rahul, the most honest among all of us, he says what? That he might quit! Why? Couse the price is hi!
Did he sell it to a big business? No! Does he trying to make it a paid SaaS? No. Can he make all the above and market it right and sell it? YES!
So where are we?
I do suggest to find a way to help the project even if it fail! What the f… community are we if we are not acting? And in my head is very simple some of us can work and the others will pay.
And @portofacil we need you here, we gonna give you the love drug to love docker 
Can we start a thread to see how and if we can be supportive for EE?
According to GitHub activity, there will be a new minor release of EE very soon.
Lots of PR have been merged in a new release 3.7.5.
That’s good news to me.
Thanks for informing. I checked it. Minor release, but gives us a strong hope.
The response here on this thread is spread across a wide spectrum. Let’s hope to bring that to the positive end. 
v3.7.5 was just the start. We’ll bring the development back on track and yes, it will need community contributions as you can see in any open source software. To make community contribution easier, we’ll improve documentation, add more tests etc.
As for integration of docker, although I agree containers bring a level of complexity, but we’re not asking you to interact with containers. EasyEngine will provide the magic to handle all the complexity and you can rest easy just enjoying the performance benefits. To recreate that magic with containers will take some planning, some trial and error and some some playing around with containers. We’ve already started with the experimentation as mentioned in the blog posts shared by @rahul286
To the ones who have made the shift to other products, it is sad to see you go. 
To the ones who still believe in the magic of EasyEngine, let’s make it great again! 
Please, hurry! I’m kinda panicking with @mriyam.tamuli’s latest update. 
Jokes apart, I’m not really sure I’ll go into this new container-based EE; instead, I plan forking the latest EEv3 to a repository in order to stick with it as long as possible — when this time comes around.