EA4 WordPress specific Profile
Open Discussion
Hello!
My request is aimed at a WordPress specific EA4 package, with at least Opcache, Memcached, the latest stable PHP version, http2, OpenSSL, curl, mbstring, Apache 2.4+, MariaDB (is that even EA related?), etc.
Which should also work with vhosting, e.g. Multisite subdirectory (*.example.com) and domain mapping of those.
A WordPress specific package will optimize a large amount of the web, as well as help WordPress hosters pick the right one for their reseller packages.
As a WordPress developer I'd be more than happy to help with composing this package.
What do you think?
There is a lot of Wordpress on the web and a lot of those sites are running on WHM/CPanel. It only makes sense that there would be a Wordpress optimized setting to get more of the web running better faster. When I first moved to a VPS from shared hosting the extra hardware resources were nice, but the ability to manage the server setting to better suit Wordpress is where all my site performance came from. Granted, not all WP installs are the same and they will still need some fine tuning, but in general I think the OP has a good idea. A blog will need some different settings than a busy ecommerce site.
This would make reselling a little easier.
I believe 54 has MariaDB 10.x supported, but it is not in EA.
There is a lot of Wordpress on the web and a lot of those sites are running on WHM/CPanel. It only makes sense that there would be a Wordpress optimized setting to get more of the web running better faster. When I first moved to a VPS from shared hosting the extra hardware resources were nice, but the ability to manage the server setting to better suit Wordpress is where all my site performance came from. Granted, not all WP installs are the same and they will still need some fine tuning, but in general I think the OP has a good idea. A blog will need some different settings than a busy ecommerce site.
This would make reselling a little easier.
I believe 54 has MariaDB 10.x supported, but it is not in EA.
Great idea! WordPress usage is a large portion of the web, and being able to optimize on that would be great. An improvement that comes with EasyApache 4 is that the profile structure is much cleaner. Profiles are a small JSON file with a simple list of packages, a description and labels, and can be shared a bit easier than EasyApache 3, so they could be created by anyone, not just from cPanel. If you happen to come up with a profile that works well for you, I'd recommend creating a thread on the forums and sharing it with the community. The more feedback about profiles and fine tuning settings about different web applications to run on the new stack the better it becomes.
Great idea! WordPress usage is a large portion of the web, and being able to optimize on that would be great. An improvement that comes with EasyApache 4 is that the profile structure is much cleaner. Profiles are a small JSON file with a simple list of packages, a description and labels, and can be shared a bit easier than EasyApache 3, so they could be created by anyone, not just from cPanel. If you happen to come up with a profile that works well for you, I'd recommend creating a thread on the forums and sharing it with the community. The more feedback about profiles and fine tuning settings about different web applications to run on the new stack the better it becomes.
Following the same request, could you also provide a profile to IPS 4 (INVISION POWER BOARD) and other forums softwares that are largely used on the web?
Following the same request, could you also provide a profile to IPS 4 (INVISION POWER BOARD) and other forums softwares that are largely used on the web?
A single memcache instance is not advised as there's no separation between clients, no security. Though it'd be lovely if they implement a way to easily start an instance per user. Though to be really useful and secure you'll probably need CloudLinux.
A single memcache instance is not advised as there's no separation between clients, no security. Though it'd be lovely if they implement a way to easily start an instance per user. Though to be really useful and secure you'll probably need CloudLinux.
I would say this is a slippery slope.. Wordpress then Joomla then SugarCrm..
I don't think we need to take the Admin out totally.. Now the ability to "make" a Profile as easy as in ea 3 in e 4 I am down..
I would say this is a slippery slope.. Wordpress then Joomla then SugarCrm..
I don't think we need to take the Admin out totally.. Now the ability to "make" a Profile as easy as in ea 3 in e 4 I am down..
Replies have been locked on this page!