Shared Revo Core?

Does anyone know of a tutorial/docs on sharing a revo core with several sites? I want to have independent installs and just share the core. Do I just upload the setup and manager folders to the new site and correct the core path or do I need to change something to ensure they don’t conflict?

On a side note I’ve been able to run a few domains off one install using different context which is awesome!

Quote from: AMDbuilder at Jul 21, 2010, 01:38 AM

Does anyone know of a tutorial/docs on sharing a revo core with several sites? I want to have independent installs and just share the core. Do I just upload the setup and manager folders to the new site and correct the core path or do I need to change something to ensure they don’t conflict?

Not yet, but it will be coming. You can do it by using different MODX_CONFIG_KEY’s for each setup (you can change this in one of the first steps in setup or manually in setup/includes/config.core.php). However, at the current time, this will only work if install the packages in each configured site, since they share a core/components/ directory. In the future we will be solving this by allowing multiple workspaces, where you can have different packages and core/components locations defined. But this will not make it into 2.0.0 unfortunately.

I don’t mind installing the packages a second time on the new site. Sharing the core folder save me disk space and inodes so it’s an automatic win in my book.

Does the key need to be anything specific or just random jiberish for each site?

Quote from: AMDbuilder at Jul 21, 2010, 09:11 PM

I don’t mind installing the packages a second time on the new site. Sharing the core folder save me disk space and inodes so it’s an automatic win in my book.

Does the key need to be anything specific or just random jiberish for each site?

You can call each config anything you want as long as it turns into a valid filename, e.g. core/config/{MODX_CONFIG_KEY}.config.php

Quote from: OpenGeek at Jul 21, 2010, 11:45 AM

Not yet, but it will be coming. You can do it by using different MODX_CONFIG_KEY’s for each setup (you can change this in one of the first steps in setup or manually in setup/includes/config.core.php). However, at the current time, this will only work if install the packages in each configured site, since they share a core/components/ directory. In the future we will be solving this by allowing multiple workspaces, where you can have different packages and core/components locations defined. But this will not make it into 2.0.0 unfortunately.

I know it’s an old thread but was just wondering if multiple workspaces made it to 2.1.1 or is still on the to do list.

Quote from: peteedley at Jun 30, 2011, 11:47 AM

I know it’s an old thread but was just wondering if multiple workspaces made it to 2.1.1 or is still on the to do list.

Still on todo list.

Quote from: opengeek at Jul 01, 2011, 03:43 AM

Quote from: peteedley at Jun 30, 2011, 11:47 AM

I know it's an old thread but was just wondering if multiple workspaces made it to 2.1.1 or is still on the to do list.

Still on todo list.

modx 2.2.8? or still on todo list?

Still on todo list.