Some simple questions

OK I currently run a site on 0.9.6.1p2

I am about to commence writing a new site and considering installing Revolution for this job. This installation will be on the same box but obviously a different domain to the existing install so I assume this wont be a problem.

Down the track when Revolution releases a stable version I would most likely migrate the other site to Revolution from 0.9.6.1.

Now from reading the install instructions I see that you install it below the web level and that it can support multiple domains.

My structure is like this:
/var/www/vhosts/mydomain1.com.au/httpdocs/
/var/www/vhosts/mydomain2.com.au/httpdocs/
/var/www/vhosts/mydomain3.com.au/httpdocs/

So does this install like this:
/var/www/vhosts/mydomain1.com.au/revolution/httpdocs/
or like this
/var/www/vhosts/revolution/mydomain1.com.au/httpdocs/

or somewhere else totally? Reading the install docs it implies you upload the files above the web root level as you have to navigate to them via a browser ie:
/var/www/vhosts/mydomain1.com.au/httpdocs/revolution/

Doe it then somehow install them below the root level?

Once installed for say mydomain1.com.au can I later migrated mydomain2.com.au to revolution (mydomain2 currently being the one on 0.9.6)?

Sorry from what I have ready I can’t really get my head around how this all fits together. Have I missed some critical document that I should have read?

Also memory requirements.
This page:
http://svn.modxcms.com/docs/display/revolution/Server+Requirements
says: Memory_limit 32MB or more

But this page
http://modxcms.com/learn/general-requirements.html
says: 64MB (or higher) Memory Limit

And this page says:
http://svn.modxcms.com/docs/display/revolution/Fresh+Installation
Make sure your php.ini setting sets memory_limit to 128M, and max_execution_time to 120

So what are the actual memory requirements and why the 3 different requirements listed?

Thanks, just trying to get my head around it.

Quote from: scarfy96 at Sep 11, 2009, 02:47 AM

Now from reading the install instructions I see that you install it below the web level and that it can support multiple domains.

My structure is like this:
/var/www/vhosts/mydomain1.com.au/httpdocs/
/var/www/vhosts/mydomain2.com.au/httpdocs/
/var/www/vhosts/mydomain3.com.au/httpdocs/

So does this install like this:
/var/www/vhosts/mydomain1.com.au/revolution/httpdocs/
or like this
/var/www/vhosts/revolution/mydomain1.com.au/httpdocs/

or somewhere else totally? Reading the install docs it implies you upload the files above the web root level as you have to navigate to them via a browser ie:
/var/www/vhosts/mydomain1.com.au/httpdocs/revolution/

Doe it then somehow install them below the root level?

There will be separate installation instructions for installing the core/ directory of MODx outside of the webroot. We do this on many Revolution sites, so you could have something like this:

/var/www/vhosts/mydomain1.com.au/httpdocs/
/var/www/vhosts/mydomain2.com.au/httpdocs/
/var/www/vhosts/mydomain3.com.au/httpdocs/
/usr/local/revolution/

Where the /usr/local/revolution/ folder is the core/ directory in the "advanced" package. Just move the core/ to this location outside the webroot, then there are several other steps (and decisions) required to then install in each virtual host directory. I’ll try and document this formally as soon as I can, but basically you run setup on one or all of them (depending if you want separate configurations/databases for each domain (a shared core setup) or you want to deploy all domains via a single database (see http://svn.modxcms.com/docs/display/revolution/Creating+a+Subdomain+from+a+Folder+using+Virtual+Hosts which applies to domains or subdomains, despite the title). You’ll just need to edit the setup/includes/core.config.php editing the MODX_CORE_PATH to /usr/local/revolution (or wherever you moved core/ to) and setting MODX_CONFIG_KEY to the name of the configuration you want to create. For shared core with multiple configurations, you’d copy setup/ to each virtual host directory and set MODX_CONFIG_KEY to a unique value for each virtual host, while for a multi-domain core, you can leave it as is and decide where the single manager interface should be installed (you’ll have a chance to choose this during installation). Obviously, for shared core, you’d run the setup/ on each domain and it will extract the necessary files where you choose for each.

Quote from: scarfy96 at Sep 11, 2009, 02:47 AM

Once installed for say mydomain1.com.au can I later migrated mydomain2.com.au to revolution (mydomain2 currently being the one on 0.9.6)?

Sure, this is not a problem at all.

Quote from: scarfy96 at Sep 11, 2009, 02:47 AM

Sorry from what I have ready I can’t really get my head around how this all fits together. Have I missed some critical document that I should have read?

Nope, we just haven’t created these docs yet as this is kind of an advanced process, and not at all necessary to run the software.

Quote from: scarfy96 at Sep 11, 2009, 02:47 AM

Also memory requirements.
This page:
http://svn.modxcms.com/docs/display/revolution/Server+Requirements
says: Memory_limit 32MB or more

But this page
http://modxcms.com/learn/general-requirements.html
says: 64MB (or higher) Memory Limit

And this page says:
http://svn.modxcms.com/docs/display/revolution/Fresh+Installation
Make sure your php.ini setting sets memory_limit to 128M, and max_execution_time to 120

So what are the actual memory requirements and why the 3 different requirements listed?

These have been changing over time (should be installable with 32M or less now) and you just caught us with some inconsistencies...

OK thanks, just one clarification then on this comment:

Quote from: OpenGeek at Sep 11, 2009, 05:00 AM

There will be separate installation instructions for installing the core/ directory of MODx outside of the webroot. We do this on many Revolution sites, so you could have something like this:

/var/www/vhosts/mydomain1.com.au/httpdocs/
/var/www/vhosts/mydomain2.com.au/httpdocs/
/var/www/vhosts/mydomain3.com.au/httpdocs/
/usr/local/revolution/

Does this mean you don’t have install instructions for installing outside webroot at the moment?

From what I have read it seems you upload and then browse to the setup or install directory and go from there but you couldn’t do this if it is installing outside the webroot could you?

We have our own virtual machine and I do have full rights on it so that isn’t an issue. The issue is I am not a Linux tech so even though I have SU rights that just makes me dangerous! (php, perl, sql etc sure but not linux servers). Hence my questions.

In Jason’s example, only the /core directory would be outside the web root (and shared by the various installs). Everything else (including the setup directory) would be in or under the web root.

I have my memory_limit set to 128M. 64M sometimes works but people have reported it as not enough on occasion. 32M is definitely not enough. The higher memory limits are necessary only for the setup phase. I’m not sure, but I think that Revo will run in 32M once installed.

OK, so to install below the webroot is it all done by the browser?

Quote from: scarfy96 at Sep 11, 2009, 05:25 AM

OK, so to install below the webroot is it all done by the browser?

Yes. Just point your browser at the URL of the setup directory (assuming that you’ve followed Jason’s advice above).

It’s a good idea to check phpInfo first to make sure of the memory_limit setting.

Quote from: OpenGeek at Sep 11, 2009, 05:00 AM

There will be separate installation instructions for installing the core/ directory of MODx outside of the webroot. We do this on many Revolution sites, so you could have something like this:

/var/www/vhosts/mydomain1.com.au/httpdocs/
/var/www/vhosts/mydomain2.com.au/httpdocs/
/var/www/vhosts/mydomain3.com.au/httpdocs/
/usr/local/revolution/

Where the /usr/local/revolution/ folder is the core/ directory in the "advanced" package. Just move the core/ to this location outside the webroot, then there are several other steps (and decisions) required to then install in each virtual host directory.

OK I have tried this and failed dismally.

First time I tried it I uploaded the advanced files and directories and moved the core to
/usr/local/modxrevolution/

I got an error saying I had to edit the config.core.php to show the path to the core. I edited it:
define(’MODX_CORE_PATH’, ’/usr/local/modxrevolution/’);

I then got an error saying to install it needed a working core.

I deleted everything, reuploaded everything and installed with the core in httpdocs.

Everything worked.

I then moved the core to:
/usr/local/modxrevolution/

and edited the config.core.php file and now it is erroring

Warning: include_once(/var/www/vhosts/treadly.com/httpdocs/core/model/modx/modx.class.php) [function.include-once]: failed to open stream: No such file or directory in /var/www/vhosts/treadly.com/httpdocs/manager/index.php on line 50

Why is it still looking there?

I have edited the config.core.php in both the httpdocs directory and the manager directory.

I am sorry, there is no doco and I can’t find anything on the forums as to how to install the core outside the root.

It just says "upload and point at the setup directory"

Well if I do that it puts the core in the httpdocs directory.

I have checked off all the server requirements and have all in accordance to the server requirements in the doco.

What am I doing wrong? What do I upload where and what do I edit to install the core outside the web server?

Thanks.

There are more config.core.php files to change (you may also need to clear the cache and your browser cache/cookies). It’s possible that you would also need to manually delete the contents of the core/cache dir (all except the index file).


I think that will do it.

When do I do that?

Do I install as per normal THEN move the core files then edit these config files (but don’t you delete the entire setup directory?)

or do I upload the other files and directories but the core ones to the new location out of the web root and then edit these files. In which case there is no connectors directory because earlier they said to use the advanced install file which has no connectors directory - it builds it.

Sorry but half instructions just create a raft of new questions.

For a fresh install.
1) Which install package do I use - the normal or advanced?
2) Which directories do I upload where?
3) Which config files do I edit before install?
4) Do I move anything after install - if so what?
5) If I do move files in 4) then which files then need editing?

Sorry to be a pain but each combination I have tried results in a different error. The only way I can get it to work is having the core directory in the httpdocs directory which sort of defeats the purpose of having one install to drive multiple domains which is the objective.

Sorry I’m not more helpful here. I actually have an install with a core outside of public_html (and a renamed manager), but I did it from the SVN version and I installed it a while ago.

Here’s what I think should work (assuming a clean start with an empty DB, an empty core/cache dir, and cleared browser cache/cookies):

1. Copy the files (including /setup to the root except for the /core directory.
2. Copy the core files to wherever you want them
3. edit all the config.core.php files
4. run setup

Here’s what I think I did.

1. Do an install with /core in the usual place.
2. After logging in once, but before doing any work in the Manager (leaving /setup in place), move the /core dir.
3. Edit all the config.core.php files.
4. Delete all files in the core/cache dir. except for index.php.
5. Clear browser cache/cookies
6. rerun setup.

I’m afraid I can’t answer your question 1. I’ve never used anything but the SVN version. I would think with the advanced install you’d do the build, then setup, then move the core, then edit the config.core.php files, clear cache, maybe rerun setup.

Hope this helps.