Multiple sites one file system **shared hosting**
Permalink
Occurred to me that I could run multiple C5 sites (which were similar or same in terms of available addons/themes) on shared hosting, using one concrete5 installation, but individual databases.
By aliasing a single site, detecting domain name the request is on, could select the right database/config in site.php, to display the appropriate website.
But would the file manager lend itself to this approach, just showing each site's files, or would it show all files? And would caching still work?
No idea if this can be done, might have overlooked a lot of things, but thanks for your help.
Ollie
By aliasing a single site, detecting domain name the request is on, could select the right database/config in site.php, to display the appropriate website.
But would the file manager lend itself to this approach, just showing each site's files, or would it show all files? And would caching still work?
No idea if this can be done, might have overlooked a lot of things, but thanks for your help.
Ollie
look up sym links
Thanks gents.
Coming at this a different way, are there any plans to allow multiple installs to use one database. It's not so much upgrades that motivate here, more managing as few backups as possible.
Thanks again.
Coming at this a different way, are there any plans to allow multiple installs to use one database. It's not so much upgrades that motivate here, more managing as few backups as possible.
Thanks again.
no. that'll get really complex really fast..
the domain mapper lets you do as much of this as we're ever going to support.
the domain mapper lets you do as much of this as we're ever going to support.
Understand, but table name prefixes of the sort wordpress allows (based on what I know of C5) doesn't seem like a massive step, given how you've put C5 together.
I'm not thinking of a DNN style system that runs multiple sites on one set of database tables.
Thanks for taking the time to discuss Franz, appreciated.
I'm not thinking of a DNN style system that runs multiple sites on one set of database tables.
Thanks for taking the time to discuss Franz, appreciated.
Did you ever find a solution? Or what did you decide on?
Took this a little way, but project got dropped.
Didn't need specific access to file manager, so didn't pursue it based on what Franz said. I just had user upload a logo in their profile page, and all that info (in their profile) form the basis for a site customisation and themes.
All the multi-site handling and site customisation was done in
config/site.php and site_theme_paths.php
Happy to post up the mods is you think it might be useful to you.
Didn't need specific access to file manager, so didn't pursue it based on what Franz said. I just had user upload a logo in their profile page, and all that info (in their profile) form the basis for a site customisation and themes.
All the multi-site handling and site customisation was done in
config/site.php and site_theme_paths.php
Happy to post up the mods is you think it might be useful to you.
What you can do is centralize the core for these installs, but each install will need its own files directory. You'll also find you may want the power to override stuff for different sites. Add-ons are licensed on a per-site basis as well and I think this would certainly be bending that license a bit far.
Centralizing the core certainly has some advantages, its easier to make a fast change across all the sites instantly. We used to suggest that to all our hosting partners that they do a centralized install that way.. These days we actually run our own sites without the centralized core. The upgrade process is graceful enough on its own that there's no real need to worry about this as we might have in the past.