Sub-Directories vs. C5 Tree Structure
Permalink Browser Info Environment
My understanding is that when you place a sub-folder off the root (and C5 is installed on the root) then its contents are not accessible to C5. Domain Mapper cannot solve this scenario, right? (I understand that the DM can map a parked domain to a page on the C5 sitemap tree.)
Previous to C5, I did a cite where I had a sub-directory that was navigated to viahttp://www.domain.com/subfolder (or, preferably:http://www.subfolder.domain.com) and this helped to separate divisions of the company - and there was no need to hide the URL as it actually helped to let the user know where they were on the site. Does this setup fall under Franz's mentioning in his screencast of "hosted partner sites for resellers." ?? My concern is not high traffic or even large databases; rather, mapping parked domains to divisions of a site for security reasons, controlling access of particular users by assigning them to user groups, etc. Obviously, individual installs of C5 would require a huge maintenance of the user groups alone - which is not acceptable.
I realize this can be done using one C5 install, the Domain Mapper addon and C5's permissions; but it would eliminate the subfolder URL (www.subfolder.domain.com) which I like. Also, I would like to learn the shared access of a single cite and the separation of databases if in fact it grew to the point of needing that for optimization in the future - perhaps I can build with that in mind. The first approach might be the best (and most cost-effective), but I am curious to know what the next level of complexity entails.
Is there a document somewhere on this topic of shared partner sites, or a contact to discuss its implementation and cost estimate?
EDIT: Found the info: It's a white paper issued to those who become host partners. Final question: If I take the Domain Mapper approach and then decide to upgrade to C5's cPanel/WHM - is there much loss and rework of the existing work? Can C5's cPanel/WHM work on Bluehost, for which I am under contract for several more months?
Previous to C5, I did a cite where I had a sub-directory that was navigated to viahttp://www.domain.com/subfolder (or, preferably:http://www.subfolder.domain.com) and this helped to separate divisions of the company - and there was no need to hide the URL as it actually helped to let the user know where they were on the site. Does this setup fall under Franz's mentioning in his screencast of "hosted partner sites for resellers." ?? My concern is not high traffic or even large databases; rather, mapping parked domains to divisions of a site for security reasons, controlling access of particular users by assigning them to user groups, etc. Obviously, individual installs of C5 would require a huge maintenance of the user groups alone - which is not acceptable.
I realize this can be done using one C5 install, the Domain Mapper addon and C5's permissions; but it would eliminate the subfolder URL (www.subfolder.domain.com) which I like. Also, I would like to learn the shared access of a single cite and the separation of databases if in fact it grew to the point of needing that for optimization in the future - perhaps I can build with that in mind. The first approach might be the best (and most cost-effective), but I am curious to know what the next level of complexity entails.
Is there a document somewhere on this topic of shared partner sites, or a contact to discuss its implementation and cost estimate?
EDIT: Found the info: It's a white paper issued to those who become host partners. Final question: If I take the Domain Mapper approach and then decide to upgrade to C5's cPanel/WHM - is there much loss and rework of the existing work? Can C5's cPanel/WHM work on Bluehost, for which I am under contract for several more months?
| Type: | Discussion |
|---|---|
| Status: | New |
None of the solutions we offer here let you share parts of the site with other parts of the site.
Push comes to shove, a concrete5 site requires a database... it's a 1 to 1 deal.
The domain mapper lets you point different domains to different parts of the site tree.
The cPanel/WHM add-on lets you automatically provision new concrete5 installs on a webserver and force upgrades.
the whitepaper you mention (and also the cPanel add on) let you share the CORE FILES of a concrete5 site.. (everything in /concrete) across your server, but you really shouldn't be messing around in those files anyway.