Hello everybody! I just recently entered the world of CMS:es and am truly glad that i choose Made simple. I intend to use it to host several sites on one server. I reckon i could install one copy of the system for each server, but I got the feeling there is a lot simpler ways of doing it.
All sites have seperate design and seperate editors. They have nothing to do with each other what so ever when I come to think of it. I have had a look at the documentation but coulden't find anything, I'm thinking i might need an addon. Any suggestions?
Thank's a lot!
Use one CMS for multiple sites?
-
streever
Re: Use one CMS for multiple sites?
Hi,
If each site has it's own domain name
then it's easy
just create a mysql database for each, or one, and use a different PREFIX for each CMS when you are doing the install
so your site that's about... oh... pet food... use the prefix "pet". your site that is about your mother, use the prefix, "mommy". This way the data doesn't overwrite.
You should use SHELL access if you have it, and follow the instructions in the manual to install to each domain.
If you mean multiple sites on the same domain, under folders, that's easy too. Install each copy to each folder.
I am sure there is a way to use one copy for EVERY site, but I recommend against that. Seems to prone to problems and errors.
If each site has it's own domain name
then it's easy
just create a mysql database for each, or one, and use a different PREFIX for each CMS when you are doing the install
so your site that's about... oh... pet food... use the prefix "pet". your site that is about your mother, use the prefix, "mommy". This way the data doesn't overwrite.
You should use SHELL access if you have it, and follow the instructions in the manual to install to each domain.
If you mean multiple sites on the same domain, under folders, that's easy too. Install each copy to each folder.
I am sure there is a way to use one copy for EVERY site, but I recommend against that. Seems to prone to problems and errors.
Re: Use one CMS for multiple sites?
Each site has it's own admin interface, it's not possible to control more than one site atm...
You will need to upload the folders/files into each domain/folder...
I have numerous subfolders in my root some have their own domain name others are subdomains in 2 diff. ways...
mit-computers.com is a folder in the root of multiintech with it's own domain name, subdomains, cmsmsdemo.multiintech.com or subfolder multiintech.com/cmsms1.1 depending on how I point my server to them...
Pagetitles?...
Each page has it's own menu text and title text can be the same or diff...
You will need to upload the folders/files into each domain/folder...
I have numerous subfolders in my root some have their own domain name others are subdomains in 2 diff. ways...
mit-computers.com is a folder in the root of multiintech with it's own domain name, subdomains, cmsmsdemo.multiintech.com or subfolder multiintech.com/cmsms1.1 depending on how I point my server to them...
Pagetitles?...
Each page has it's own menu text and title text can be the same or diff...
-
kristoffernolgren
Re: Use one CMS for multiple sites?
I like the database-approach (my host pays by the MB) Though i am not very good at the sql-stuff, is it possible to just use the installation wizard, but with a different prefix?
How about file uploads etc? Is there possible to set accesss for diffrent users and diffrent files aswell? Anything else i need to think about?
How about file uploads etc? Is there possible to set accesss for diffrent users and diffrent files aswell? Anything else i need to think about?
-
iNSiPiD
Re: Use one CMS for multiple sites?
Kristoff,
As Mark stated there is only one admin interface per site. This means that a full CMS installation is required for each site.
Each CMS installation can only handle a single config.php which in turn handles only a single site.
It would be nice if in the future a mutli-site front-end was implemented that could manage more than one site/installation but it' snot possible now.
As Mark stated there is only one admin interface per site. This means that a full CMS installation is required for each site.
Each CMS installation can only handle a single config.php which in turn handles only a single site.
It would be nice if in the future a mutli-site front-end was implemented that could manage more than one site/installation but it' snot possible now.
Re: Use one CMS for multiple sites?
What if you set up your install like this:
You have your main CMSMS site - mycms.com
and a couple of domains you host:
domain1.com
domain2.com
domain3.com
Your hosting dir:
path/to/mycms
domain dirs:
path/to/domain1
path/to/domain2
path/to/domain3
mysql db:
cmsms
mysql table prefixes:
mycms_
dom1_
dom2_
dom3_
Copy all of the CMSMS Core and any additional Modules into mycms.com and do an install.
Copy only the Admin, tmp and uploads folder/subfolders from mycms.com to domain1.com, domain2.com and domain3.com.
Copy the files from the root directory of mycms.com into domain1.com, domain2.com and domain3.com and edit the config.php to reflect the proper paths and db prefixes for each.
Would this work?
Nullig
You have your main CMSMS site - mycms.com
and a couple of domains you host:
domain1.com
domain2.com
domain3.com
Your hosting dir:
path/to/mycms
domain dirs:
path/to/domain1
path/to/domain2
path/to/domain3
mysql db:
cmsms
mysql table prefixes:
mycms_
dom1_
dom2_
dom3_
Copy all of the CMSMS Core and any additional Modules into mycms.com and do an install.
Copy only the Admin, tmp and uploads folder/subfolders from mycms.com to domain1.com, domain2.com and domain3.com.
Copy the files from the root directory of mycms.com into domain1.com, domain2.com and domain3.com and edit the config.php to reflect the proper paths and db prefixes for each.
Would this work?
Nullig
-
iNSiPiD
Re: Use one CMS for multiple sites?
Nullig, sure. But what you're essentially doing is installing the CMS in multiple locations.
Using the same database to handle multiple installations is, of course, possible - though not recommended for obvious reasons. It'd only take corruption in one DB for you to potentialy lose all your data.
Unfortunately there is, as yet, no way to manage and run multiple installations from a single installation.
The good news, however, is that I don't think it would take much to to tweak the installer to handle multiple DB and config file installations; and build a administration screen that could let you manage them. The only proviso is that you'd still need some core files in each location and the provision for individual module prefs.
As Martin Luther King once said, "I have a dream".
Using the same database to handle multiple installations is, of course, possible - though not recommended for obvious reasons. It'd only take corruption in one DB for you to potentialy lose all your data.
Unfortunately there is, as yet, no way to manage and run multiple installations from a single installation.
The good news, however, is that I don't think it would take much to to tweak the installer to handle multiple DB and config file installations; and build a administration screen that could let you manage them. The only proviso is that you'd still need some core files in each location and the provision for individual module prefs.
As Martin Luther King once said, "I have a dream".
-
alby
Re: Use one CMS for multiple sites?
No, I must edit fileloc.php also; I don't remember now but there are other part.Nullig wrote: What if you set up your install like this:
You have your main CMSMS site - mycms.com
and a couple of domains you host:
domain1.com
domain2.com
domain3.com
Your hosting dir:
path/to/mycms
domain dirs:
path/to/domain1
path/to/domain2
path/to/domain3
mysql db:
cmsms
mysql table prefixes:
mycms_
dom1_
dom2_
dom3_
Copy all of the CMSMS Core and any additional Modules into mycms.com and do an install.
Copy only the Admin, tmp and uploads folder/subfolders from mycms.com to domain1.com, domain2.com and domain3.com.
Copy the files from the root directory of mycms.com into domain1.com, domain2.com and domain3.com and edit the config.php to reflect the proper paths and db prefixes for each.
Would this work?
Sure you have problem in all modules with "file" templates.
Alby
