multiple sites on 1 install

[Ted]

That shouldn't cause an issue, I don't think.  dirname(__FILE__) SHOULD take symlinks into account, though you should probably test to make sure. 

[lemkepf]

The only problem will be when you update a module, you'll have to go to each individual system and hit the upgrade button.

Hmmmm... that might be an issue. Can you think of a quick and easy way to do this automatically?

[alby]

The only problem will be when you update a module, you'll have to go to each individual system and hit the upgrade button.

Hmmmm... that might be an issue. Can you think of a quick and easy way to do this automatically?

Symlink modules/News, modules/EllNav, modules/CSSMenu and modules/FckEditorX.
Note: not "modules" but subdirectory

That shouldn't cause an issue, I don't think.  dirname(__FILE__) SHOULD take symlinks into account, though you should probably test to make sure. 

I have error in admin section:

Code: Select all

echo dirname(__FILE__); exit;

path is relative to central position

Alby

[lemkepf]

The only problem will be when you update a module, you'll have to go to each individual system and hit the upgrade button.

Hmmmm... that might be an issue. Can you think of a quick and easy way to do this automatically?

Symlink modules/News, modules/EllNav, modules/CSSMenu and modules/FckEditorX.
Note: not "modules" but subdirectory

No... not the files, but actually execute the modules "upgrade" function against that users DB.

[alby]

No... not the files, but actually execute the modules "upgrade" function against that users DB.

Hummm...
In cms_modules table (users DB) there is a module version.
Maybe (?) there is a check version on this value for update file+db.

Alby

[lemkepf]

OK... so is there a way to automatically upgrade the modules if they are updated?

When would there be a time when you wouldn't want to upgrade right away?

Uhm... thoughts on how i could go about doing this?

[rebaf]

I can't help but feel that for large sites it would be better to use a new DB for each.

Can you explain how this would be better? Performance? Simple management? It probably is easier to code a multisite management front end rather than have to make changes in most scripts and in hundreds of places. But that front end is not the solution I would like to see.

My interest is to be able to manage multiple systems, which share many of the same characteristics, and do it with a single database. That's what I thought this thread was about.

If you are providing a hosting solution and want to provide a CMS for individual accounts separating the databases is definitely the way to go, but wouldn't you also want to separate the code base? Otherwise any time the code base changes all users would be forced to be upgraded at the same time.

Also, any opportunity to share information between sites is very limited. The only time this is possible is when a site is created. You can copy data from an existing site. From that time on each site is independant - for better or worse.

I'm in favor of making it all in the same tables.  That allows us to not have to force people to setup anything extra on our end to add a new site.  Just create it and it goes.

However, that does mean that site id has to be added to most tables and a lot of stuff is going to break.

Unfortunately yes a lot of changes, but the result is extremely flexible.

As far as I know, all of the other CMS applications are able to be installed under multiple databases. Adding a front end to manage that would be an advantage for CMSMS. Several of the other CMS have or are implementing multisite through the manipulation of file prefixes. This approach can be developed, possibly providing a front end management facility. Other than possibly some of the proprietry CMS, no CMS I know is attempting to provide multisite the way it has been discussed here. This could truly set CMSMS apart. Also, this idea doesn't prevent or hinder the development of the multiple database front-end.

Sorry to stir the pot again, but I think the multisite concept is very interesting and worth getting right.

[kishman155]

the only thing you need to manage multiply installation of CMSMS is the config.php

I put the config files from CMSMS installations into the root directory of CMSMSManagment Installation
like this config1.php,config2.php

change database locations from localhost to the domain.

if i want to change something (notcontent) like creating users I change the fileloc.php

Code: Select all

define("CONFIG_FILE_LOCATION", dirname(__FILE__).'/config1.php');

Like this I Am able to make changes fom one account managing CMSMS.
Nice things I am planning to do is to make a module like modulinterface wich checks
what version of module is installed on the Management CMSMS and what is on Server.

If there are diferent Installation there could be an saveupload funtction with ftp wich change the foldername of the module like backup_foldername(with this trick moduleinterface is not able to load module twice) and now you could perform installation in the moduleinterface.

I thing its not much work to make an installation wich change the configfile inside the CMSMS.

For Administrating multiply Installations there is no need for editing content it must be enough to chang properties
and things like name, Menuname,template, alias .


mfg
kishman155 

[lemkepf]

I can't help but feel that for large sites it would be better to use a new DB for each.

Can you explain how this would be better? Performance? Simple management? It probably is easier to code a multisite management front end rather than have to make changes in most scripts and in hundreds of places. But that front end is not the solution I would like to see.

Uhm.. simple management, modules wouldn't have to changed, etc.

My interest is to be able to manage multiple systems, which share many of the same characteristics, and do it with a single database. That's what I thought this thread was about.

Yea... i think this should be broken up into 2 threads. But i think i have my questions answered already.

If you are providing a hosting solution and want to provide a CMS for individual accounts separating the databases is definitely the way to go, but wouldn't you also want to separate the code base? Otherwise any time the code base changes all users would be forced to be upgraded at the same time.

Exactly! We do this for things like PHPbb, wordpress, phplist, etc. When a new version is released we upgrade it in one place and all our clients have the upgraded version. (we dont' do this for major upgrades, like from php1x to php2x... those are seperate installs. )

[rebaf]

I can't help but feel that for large sites it would be better to use a new DB for each.

Can you explain how this would be better? Performance? Simple management? It probably is easier to code a multisite management front end rather than have to make changes in most scripts and in hundreds of places. But that front end is not the solution I would like to see.

Uhm.. simple management, modules wouldn't have to changed, etc.

I agree the amount of work required to make it work is high, but the potential flexibility is also very high. If I had access to unlimited databases it would not be the same issue, but I can't be certain that I have multiple databases available in every circumstance where I would like to deploy CMSMS. This seems a reasonably common circumstance for administrators responsible for subdomain and directory implementations. Wasn't that the sort of circumstance that started this thread?

Of course, if I'm the only one pushing this idea then I'll just take a low profile and look for another way to meet my requirement.

[roman]

i think will by good for every instalation of web new directory and in this place all relevant files and directories:

Code: Select all

config.php,
tmp/templates_c/
tmp/cache/
modules/news/templates/
modules/anothermodule/anotherspecificdir/
uploads/
images/

... and in admin panel can grow submenu put, import, export site, with zip, backup functions

[roman]

all files in one directory will good for lock cmsms other directories against changes from "web's". and apache rules for permissions in directories...

also dbbackup can by in this dir (with hash name)

[godzone]

Has anyone come up with what needs to be done to have one install, multiple databases etc as suggested here.

This is how we run typo3, just the one install and each site has a symlink to typo3_src.

Can this be done with cmsms, if so what needs to be symlinked.

At present, I am installing all the files for each user and that isn't going to scale very well.

[Pierre M.]

May be the config.php is the only specific file not to symlink.
Of course you need separate cache and so.
Of course you may still install "all the files for all users" too for modules unless your symlinking generator is very smart.

Pierre M.

[Gregware]

Hello,

I don't know if it possible? Using ".htaccess" and redirect by URL to virtual subfolder using Rewrite Condition.
Using differents tree in pages admin, and showing tree by users.

English is not my mother tong and I don't know if i'm verry clear!

It is juste a idea! I do not know if it is possible, but it seem to be a possible way! no?