What about a list of Host Providers that can run Modx Revolution?

Hi

I recently was in contact with Startlogic support because of a PDO_MYSQL error I was receiving. They told me that they do not have PDO_MYSQL installed but plan on installing it but did not have a time frame for it. So it seems that I will for now install Evolution until Startlogic either installs PDO_MYSQL or I choose to go with another Provider.

It would be great if a list of Hosting Providers that covered the requirements for running Revolution was added to this site. We could use it to encourage our Hosting Providers to take care of the requirements for our own sake of running Revolution but also as an added PR for them as they would make the Can Run Modx Revolution Hosting Provider list. They all want additional customers and additional PR is always helpful for them. Certain requirements might need some extra weight showing that other software is also planing on using it.

We could e-mail our providers and encourage them to get their name on the list.

What do you say?

Paal Joachim

You mean something like this list: http://modxcms.com/community/partners/hosting.html ?

Great!
Yes! That is exact that I mean!

Does that list cover the requirements for Evolution and Revolution?

Quote from: Paal_Joachim at Jul 10, 2009, 07:35 AM

Does that list cover the requirements for Evolution and Revolution?

At least Evolution, and most likely Revolution as well, though until we finish with the beta release phase of Revolution, we will not have a complete understanding of what environments can run Revolution (or specific features of Revolution). We need more folks to try it in more environments before we can be sure all the problems folks will encounter, just as you have...

I’ll try and collect more of what we know this weekend into this page in the documentation; I’ll also start a page with specific hosts known to run Revolution, and reply back here when it’s posted.

Great!!

hum... to expand on that idea some it would be interesting if modifications from the stock hosting were noted (custom php.ini to increase memory limit, disable register_globals, etc.)?

Quote from: AMDbuilder at Jul 12, 2009, 08:58 PM

hum... to expand on that idea some it would be interesting if modifications from the stock hosting were noted (custom php.ini to increase memory limit, disable register_globals, etc.)?

Those are indeed indicated in the existing Server Requirements page. More to come...

Quote from: OpenGeek at Jul 13, 2009, 12:05 PM

Quote from: AMDbuilder at Jul 12, 2009, 08:58 PM

hum... to expand on that idea some it would be interesting if modifications from the stock hosting were noted (custom php.ini to increase memory limit, disable register_globals, etc.)?

Those are indeed indicated in the existing Server Requirements page. More to come...

I think the idea is that it would be nice to have a list of specific things that you need to do to make a host compliant with server requirements (and/or to optimize it for MODx). For example, Hostgator has register_globals on, so it needs to be turned off. On Hostgator this must be done with a php.ini file in the main directory AND the manager directory, and cannot be done via an .htaccess file. It is useful to know these host-specific details.

Also, on Bluehost, when you create a database, the collation is set to Swedish. It is important to use phpMyAdmin to set it to utf8_general_ci before installing MODx, to save yourself a headache later if you want to use utf8 content. What I think is needed is a brief but clear setup tutorial for a host before it can go on a ’recommended’ list.

Quote from: rfoster at Jul 13, 2009, 08:43 PM

I think the idea is that it would be nice to have a list of specific things that you need to do to make a host compliant with server requirements (and/or to optimize it for MODx). For example, Hostgator has register_globals on, so it needs to be turned off. On Hostgator this must be done with a php.ini file in the main directory AND the manager directory, and cannot be done via an .htaccess file. It is useful to know these host-specific details.

(cringe) I will withhold my nasty comments on the hosts that require php.ini files per directory, other than to say that this does not protect any files in directories you do not put one in. Every security vulnerability I’ve ever seen in MODx did not occur in either of the directories you mentioned. This is a false sense of security because putting it in those two directories fixes normal front-end requests and removes the warning in the manager; it does nothing to prevent actual attacks to directly accessible php files, say within TinyMCE or to the Reflect snippet directory.

Regardless of this rant, I do not think it is within the scope of the project to track this for individual hosts, but as long as I don’t have to organize or maintain it, anything is possible...

Quote from: rfoster at Jul 13, 2009, 08:43 PM

Also, on Bluehost, when you create a database, the collation is set to Swedish. It is important to use phpMyAdmin to set it to utf8_general_ci before installing MODx, to save yourself a headache later if you want to use utf8 content.

That’s pretty much an issue with any host that runs MySQL with the default configuration.
Quote from: rfoster at Jul 13, 2009, 08:43 PM

What I think is needed is a brief but clear setup tutorial for a host before it can go on a ’recommended’ list.

I think once we define these server requirements in more detail, the information can be used by hosts as guidelines for this.

Onesmarthost works fine with the current version of Revolution, with no changes needed.