Manager Context

Two short questions:

With 0.9.7 is it possible to have the manager as a subdomain via and separate context?

and is it possible to change the name of the manager, for example: mydomain.com/admin instead?

Quote from: Mallmus at Dec 04, 2007, 12:31 AM

With 0.9.7 is it possible to have the manager as a subdomain via and separate context?

and is it possible to change the name of the manager, for example: mydomain.com/admin instead?

Yes and yes. I’ve run one with the manager as area51/. I have not run a manager as a standalone subdomain yet, but I don’t see any obvious reasons why it wouldn’t work as is.

In fact, I’m running a single core/ located outside of my web server document root for maximum security (and managed by SVN directly), and several different configurations (different databases, caches, managers) from that single core successfully right now.

I’m running a single core/ located outside of my web server document root for maximum security (and managed by SVN directly), and several different configurations (different databases, caches, managers) from that single core successfully right now.

wow, that sounds hyper secure - what’s the nature of the website that needs this much security? - or is it just because you can?

Do you know if this sort of stuff will be documented/wikied in conjunction with the 0.9.7 release? - has 0.9.7 got any documentation yet?

Documentation for 097 will be much more extensive. The advantage of running one core out of webroot extends far beyond security, though security is certainly a very good reason on it’s own. You can run multiple sites off one core install, so an upgrade for one site upgrades them all.

For some preliminary ideas of some of what’s going to be possible with 097, I suggest starting at Jason’s blog post then peeking at the 097 Roadmap.

I am new to modx and I am interested in how to setup multiple sites under the one install.  eg: www.somesite.com.au and www.othersite.com.au
Thanks,
Troy

Quote from: OpenGeek at Dec 04, 2007, 03:13 AM

In fact, I’m running a single core/ located outside of my web server document root for maximum security (and managed by SVN directly), and several different configurations (different databases, caches, managers) from that single core successfully right now.

i have a little information about security, would someone tell me how locating the core to outside of document web root cause more security?

Quote from: AHHP at Aug 23, 2008, 03:45 PM

Quote from: OpenGeek at Dec 04, 2007, 03:13 AM

In fact, I’m running a single core/ located outside of my web server document root for maximum security (and managed by SVN directly), and several different configurations (different databases, caches, managers) from that single core successfully right now.

i have a little information about security, would someone tell me how locating the core to outside of document web root cause more security?

It would be unavailable to the web server directly, so any exploits depending on accessing a script would be rendered useless on everything stored in the core. Of course, sloppy programming could still lead to vulnerabilities despite having the files unavailable to the web server document root, but that is always the case regardless and it never hurts to make it that much harder to exploit.

Hello again - this thread’s nearly nine months old!

I’ve just installed Revolution Alpha 3 and I’m still trying to get my head round Contexts.

When prompted to specify the manager context location and the web context location I decided to make some changes, my server path leading to the MODx installation is setup like something like this: /bla/blabla/blablabla/bla/12345/domains/firstdomain.com/html/ and I wanted to change the location of just the web context to this: /bla/blabla/blablabla/bla/12345/domains/otherdomain.com/html/ leaving the manager context on firstdomain.com

After changing the web context path I was expecting to be able to go to otherdomain.com and be able to view the document with ID 1 - but instead I get a 403 Forbidden page error and fins a config.core.php file at its location containing:

I was quite pleased that MODx had been able to put a file somewhere completely different on my sever, but otherdomain.com wasn’t showing the website, instead firstdomain.com/ was showing the web context, and also firstdomain.com/manager was showing the manager context.

I’m not sure what I’ve done wrong here, anybody got an idea?

Also, what is the AJAX Context, and what would the purpose of changing its location be?

Finally, once I’m in the manager I can add a totally new context, such as thirddomain.com, which I can then start adding documents into - but how can I make /bla/blabla/blablabla/bla/12345/domains/thirddomain.com/html/ load this context?

Quote from: Mallmus at Aug 31, 2008, 04:09 AM

After changing the web context path I was expecting to be able to go to otherdomain.com and be able to view the document with ID 1 - but instead I get a 403 Forbidden page error and fins a config.core.php file at its location containing:

<?php
define('MODX_CORE_PATH', '/bla/blabla/blablabla/bla/12345/domains/firstdomain.com/html/manager');
define('MODX_CONFIG_KEY', 'config');
?>

I was quite pleased that MODx had been able to put a file somewhere completely different on my sever, but otherdomain.com wasn’t showing the website, instead firstdomain.com/ was showing the web context, and also firstdomain.com/manager was showing the manager context.

It should have also extracted index.php to this location. I assume you got the advanced package? It is the only package that is meant for deploying the reference contexts into custom locations. And I assume that you did not select "files already in place" on the installation options page? This would only apply if you didn’t change the default locations.

Quote from: Mallmus at Aug 31, 2008, 04:09 AM

Also, what is the AJAX Context, and what would the purpose of changing its location be?

All AJAX manager requests are routed through the connectors context, and it can serve as a general purpose context for allowing custom interfaces to take the same actions as can be made in the reference manager implementation that is provided. And the purpose is the same as the rest, to allow the physical location to be customized for whatever reason.

Quote from: Mallmus at Aug 31, 2008, 04:09 AM

Finally, once I’m in the manager I can add a totally new context, such as thirddomain.com, which I can then start adding documents into - but how can I make /bla/blabla/blablabla/bla/12345/domains/thirddomain.com/html/ load this context?

You can either copy the index.php and config.core.php to this location and modify it to load the specific context in the $modx->initialize(’web’) statement, or you can serve the domain from a single location and use a plugin to detect the http_host and then use $modx->switchContext(’myCustomContext’); to dynamically change it. Please note there are significant improvements in this functionality in recent revisions (after alpha 3).

It should have also extracted index.php to this location. I assume you got the advanced package? It is the only package that is meant for deploying the reference contexts into custom locations. And I assume that you did not select "files already in place" on the installation options page? This would only apply if you didn’t change the default locations.

Actually I tried the modx-2.0.0-alpha-3.zip - the modx-2.0.0-alpha-3-advanced.zip file only has a core and a setup folder, should I overwrite modx-2.0.0-alpha-3.zip’s core and setup folders?

Is there an SVN location for these and also the 0.9.6.2-rc2? I can’t seem to find it anywhere....