WordOps is quite alive, you can check their Slack channel. Basically the domain got suspended by their registrar and they still can’t get it back. They just released an update a few days back that is working flawlessly.
1 Like
I’ll definitely give WordOps a try down the line, but I admit I was a little discouraged by the domain name issue - it just didn’t fill me with confidence that it had a future, although @virtubox’s involvement is a plus. I’ve migrated 20 sites to EE4 then to Webinoly in the space of about a month, and that’s enough migrating for now. 
My Webinoly server is purring along nicely.
I’ve migrated out of Webinoly and into my own docker stack. EEv4 is great but it’s too bulky for my taste. My WP sites are idling at 10mb of ram and MariaDB is around 50mb.
Hey, interesting approach with your own docker stack? I’m a big fan of docker and using it on some other projects. Why not share it and have a few interested people improve it together?
Interesting to read that. I just noticed it’s made by Delicious Brains. I had my experience with them through their WP Migrate DB plugin which holds me off from instantly jumping on any boats they control. Though will be interesting to see how SpinupWP develops.
Hi, thanks for your interest. It’s nowhere near ready for other people to use it yet, the main bash script has lots of bugs I’m working on.
First of all: I’m a big fan of docker. I can imagine people having a hard time getting used to the changes involved by the nature of docker I think it’s totaly the right thing to switch to it.
Apart from that I’m also wondering how that Switch to EEv4 happened in the way it happened. I have to admit, I don’t have a deep insight into the project and what it means for the company behind from an outside perspective I’d say the switch overall was a bit unlucky. For a final release you’d expect to have at least the most important featureset onboard or otherwise put big warning letters on every public post that says stuff like “Be aware that this is a complete rewrite and we start off with a very limited featureset” naming all the important stuff missing like (s)ftp to single sites, editable sites, switching types etc.
In addition the reliability of the update script of course is a problem. It’s kind of the central tool that has to work reliably.
I can remember having read about funding problems for the project in the past and can only imagine that it’s hard to keep it up. That’s why I try to stay soft on the critics. I’m sure the guys behind this, especially @rahul286 are investing a lot of time and energy to try to keep this free and open source. I appreciate that but I also agree with what @terencemilbourn said. I wish there was a commercial model in addition. One that also is affordable for the smaller customers, probably enables some additional features or support but foremost opens the ability to put this project on a solid funding base. With all the other projects around I think there’s still a lot of potential for such a project.
I’ll definitely stay with EE as long as I can keep my sites running and i’m totally willing to work around some glitches if only in thanks for what the guys did for the community in the last years.
1 Like
I’ll take a look. Thanks for the heads up.
By the way, before I moved back to Scotland I lived 35 years in St Ives near Ringwood and think the stretch of coast along the Purbecks is some of the nicest in the country.
If Webinoly turns out to be at least half as nice, I’ve found a watch. 
Hi All,
Rahul from EE team here.
First I agree v4 is not as smooth as expected. We aim to build things “that just works” and this is not the case this time.
I agree with @mram checklist. Especially stability aspect. We have slowed down release cycle also for now. Because we want to get 4.1 updates, when available, rolled out without an issue!
That being said - we have v4 on most of our sites.
I do not have ETA for coming features. But stability is what our #1 and can be said the only goal for now.
I see some people are interested in running things with docker-compose. You may try https://github.com/10up/wp-local-docker-v2 and https://github.com/10up/wp-local-docker which can help you in that.
The goal of EasyEngine project and team is to make your life easy. Not push EasyEngine software down your throat! 
If we come across any projects like 10up’s or WordOps, we will continue to recommend them.
3 Likes
Thanks for the update. Looking forward to the next release.
It tends to be the little things that frustrate so badly. The update that won’t update without an error, or the fact that you have to edit the NginX config for every site just to make it ‘leverage browser caching’, which at worst should have been a command line switch, or at best the default condition. There seems to be no development feedback that fixes these things or lets you know how important they are to the user.
Hi @Helmi, if you’re still interested in my docker stack then come check it out. It’s nowhere near as polish as EEv4 but built with EE as the inspiration. Special thanks to VirtuBox for the NGINX and PHP configs.
For now it only works with a fresh install of Ubuntu 18.04.
I saw the hassle coming early, left EE for Webinoly in december.
Unfortunately the lack of communication and a very unstable product made me leave.
Same here, now running WPMU subdomain with mapped domains smoothly with webinoly.
Well I also left EE4, first the migration failed, then I saw that a fresh install required a lot of work to get a server with multiple websites working properly. In my case the docker approach increase the amount of work to config many websites. EE4 seems to leave the easy-lightweight path which is very frustrating.
Anyway, I used EE for years and I’m very grateful to the project contributors. Now I’m using WordOps which is a great upgrade of EE3 but keeps the same smooth workflow for me.
I made my own stack because EE had a lot of features that I don’t use; #1 being the most annoying.
- NGINX auto redirection to first made site
- Don’t need MailHog (since I don’t dev locally anymore and use mailtrap.io)
- Don’t use multisite (it’s messy when exporting/importing a network)
- Don’t use redis
- Don’t use New Relic (whatever that is)
And more importantly #6 EEv4 installs a bunch of dependencies into the host OS. I tried to make my stack independent from the host by installing everything into my images.
hi Chip, or anyone… how many sites can you run on a Wordops install… say with 2meg or 4 meg of RAM? Thanks!
How to resolve git hub issue.