EasyEngine v4 and whatnot


#1

Hi. There are some things I’d like to know before switching to v4:

  1. is v4 now the only version available?
  2. How caching works and how is Nginx related to it? (it’s because I liked --wpfc over --wpredis)
  3. is mobile caching separated from desktop caching?
  4. is it possible to turn off Redis full page caching (but still use object caching) and use a plugin like wp super cache or wprocket (for the sake of mobile caching separation)
  5. what security tweaks can be or should be applied. I assume tutorials are old and the v4 now includes some of the tweaks from the tutorials?

Thanks


#2

Can you please go through https://easyengine.io/handbook/?

We tried to cover a lot there.

Still below are some quick answers:

  1. is v4 now the only version available?

Yes. More details in https://easyengine.io/handbook/v3-to-v4-migration/

  1. How caching works and how is Nginx related to it? (it’s because I liked --wpfc over --wpredis)

Start with https://easyengine.io/handbook/internal/request-cycle/ The redis-cache was documented in past here https://easyengine.io/blog/easyengine-3-3-full-page-redis-cache/

  1. is mobile caching separated from desktop caching?

Not by default. It was never part of v3 or past EE release. We recommend using responsive design. Even better PWA https://en.wikipedia.org/wiki/Progressive_web_applications

However, you can tweak cache keys via custom nginx conf. This document may help for correct file location - https://easyengine.io/handbook/global-filesystem-structure/site-filesystem-structure/

  1. is it possible to turn off Redis full page caching (but still use object caching) and use a plugin like wp super cache or wprocket (for the sake of mobile caching separation)

Yes, but it will need efforts on your end. You can create a site with redis cache, remove redis caching code from nginx conf. That will bypass requests to WordPress and your caching plugin. There are other ways also, but you will need to play with nginx conf for wp super cache / wprocket anyway.

It will be a fraction of effort to do mobile/desktop cache separation in redis-cache itself.

  1. what security tweaks can be or should be applied. I assume tutorials are old and the v4 now includes some of the tweaks from the tutorials?

Whatever we feel is “must have” has been always part of EE core. We do use and recommend Cloudflare wherever possible!


#3

How long do you expect EEv3 to remain available for people like me who just can’t jump to EEv4, due to Docker limits? (For instance, I have some customers with 200+ domains in a single VPS.)

Thanks.


#4

We do not support v3 in any way except fixing critical security vulnerabilities. The security fixes will be provided until January 31, 2019 .

After that v3 servers can keep running as long as they can. You can create fresh servers with v3 installer even after that. It’s just there will be literally zero support and update.

As v3 has its own nginx-builds, they will get outdated too.

If 200+ sites is only reason to not move, we might have a good news for you at some point.


#5

This seems like a good place to ask this question, as it applies to “whatnot” :wink:

Why is it EEv4 was released for the already aging OSs and not for the newer Ubuntu 18.01LTS/18.10 or for Debian 9?


#6

EE can works on every Linux OS which can run Docker and has PHP interpreter.

We just don’t have time to test with other platforms. Next month, when new release settles, we will add tests for platforms and support them in our installer https://github.com/easyengine/installer

For time being, you can follow “Manual Install” method here on any *nix platform https://easyengine.io/handbook/install/

It should work. If you run into any issues, we will be happy to help to fix issues. :slight_smile:


#7

Jesus, you guys messed it all up for me.
I literally have TONS of sites running EasyEngine on a bunch of OVZ and whatnot servers that do not support Docker.


#8

@Chip You can keep using v3. Nobody is forcing you to update to v4.

v3-to-v4 migration is optional!

You may also join folks at https://wordops.org/ who are working on a v3 fork. :slight_smile:


#9

Fantastic, kudos to the guys working on WordOps and thanks for pointing me in that direction.
Cheers.

P.S. Really sad to stop using the original EE though - so used to that commands and what not. Docker’s stuff is really good, but it won’t run on the majority of OVZ/LEX budget VPS providers.


#10

It’s fine. Thanks for using EasyEngine thus far.

We are in touch with WordOps team. Once the fork is ready, we will update all EasyEngine resources to point users to them. :slight_smile:


#11

This is great news. WordOps fork. However I will use v3 for a while and then after the support ends will switch to WordOps. Also, I plan on using v4 too. Therefore it all works out for me.

However, I’d like someone to point me where to read more about why, or in what ways docker is better and when the WordOps fork would be better.
Thanks


#12

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.