-
☆ A M B ☆
- 24,524 Posts
In the first place, MODx can’t "mix up" with their stuff. It’s all run from two index.php files, the one in the site root (wherever you choose to install MODx) for the front-end, and the other from its manager directory for the Manager back-end. Nothing at all in MODx can access anything outside of its own files and its own database, unless somebody deliberately codes a script to do so (which of course would be the case with anything they have on their server). Now if they can’t depend on their own developers keeping their own code clean, that’s another matter...
I usually have at least four or five different MODx sites under development, as well as one or two different versions being checked out from SVN, alongside several other applications such as ecommerce packages (magento etc.) or forum packages (vanilla etc.) and anything else that may have caught my attention (lots of free toys on the Internet!), all on one little iBook with a MAMP installation. Nobody ever interferes with anybody else. On my remote Solaris VPS I’m currently hosting several different MODx sites as well as a Vanilla forum for one of them, and again a few experimental web applications.
MODx even uses its own table prefixes (modx_ by default, but you can change this to whatever you want during installation) so that you can have different applications using the same database that use the same base table names without getting them mixed up. For example, if you by chance have another application that uses "web_users" as a table name, that’ll be fine, since MODx uses "modx_web_users". The MODx and Vanilla installation I mentioned before are using the same database with no problems. (before anybody asks, no, they’re not integrated; the MODx site doesn’t use a login for anything so just Vanilla handles the user management stuff)
-
☆ A M B ☆
- 24,524 Posts
Well, I can’t answer for the reverse proxy bit, but I don’t see why not. All it does is generate ordinary web pages that get passed on to the server like any .html file. The install folder in the archive has .sql files for installation and upgrading; they are plain .sql dump files so you can see the table structure from them. As far as php.ini goes, you’ll get a warning if Register_Globals is on, but other than that any standard php.ini configuration should work. Some things require the GD libraries, but you can live without them if necessary.
Really, the whole thing is open source, as in the PHP source code is wide open; it’s just a bunch of PHP scripts that get run from the index.php files. At least in 1.0 Evolution, they don’t do anything fancy at all. The manager uses a bunch of javascript, but even there it’s nothing particularly unusual.
Try this... maybe it will help.
http://www.sottwell.com/how-modx-works.html
and they are very worried about ModX mixing up with their stuff. So they would like to know if they can install it on another server using a proxy, and they wish to install it themselves using a tarball package. Is that easy to do, and what are the requirements ? To be completely honest this is not totally my cup of tea, as I’m more into GUI & sales. My coder has pig flu (or is visiting Hawaii with girlfriend, no idea) and won’t even pick up the phone, so I figured out this would be a nice place to ask 
The guy told me he has a team of top coders so I wouldn’t want to look too much stupid when I meet them next week.
- but not with me !