CMS Made Simple Forums

To discuss multi client capabilities of cmsms i'm looking for
interestet guys with experience in multi homing cmsms
installations on a single webserver in different directorys.

I'm currently heading for an easy way to put togehter all
the cmsms stuff which could be shared between cmsms
installation on a single machine.

If you are interested then please apply to this discussion,
i will explain my plans as soon we get enough audience.

Michael

Me too!

I think its a good idear.

something you can find on this forum for another CMS:
http://www.xoops.org/modules/newbb/viewtopic.php?topic_id=40483&forum=7&post_id=177561#forumpost177561
One physical instalation, many databases for very domain name. But you will have problem with for example upload directory for clients fieles...

Please discuss this, particularly about implementation details.  This is one thing I would like for the 2.0 rewrite and it would take some burden off if you guys knew how to handle it properly...

Thanks!

I have two different approaches in mind,
one for short and the other one for the
long run.

I want to discuss them first, i hope
you guys agree.


short run:
a single installation directory, which gets
soft linked (on *nix and bsd os) from other
directorys,  with a single config.php, .htaccess
and uploads  directory

some pros:
less files, easy maintainable
installation.

More pros appreciated by you..


some cons:
many softlinks, plugins are
loaded in each cms, even those
who may should not.

More cons appreciated by you..


long run:
a single installation directory with real
multi client caps.

a perfect multi client cms should not consist
on plenty filesystem soft links, plenty databases
and plenty directories. But it could.

The question, or better, my question at this
time is: is it better for a multi client cms to
have all in one place (sharing one database,
one upload folder, etc) or have something
more seperated (abilities to have databases
even on other host systems, have nfs network
shares for uploading files and may web-share them
across networks)

What do _you_ think ?

Michael

I think it would be nice to have plugins and modules at one place and share it with other installations of CMSMS.
A central config file for adodb wher it stored and an admin pannel for all would be nice but i think its very hard work to implement those thing.
The database must get splittet and the permissions had to say wich site content the user could administrate.
There had to be a filter which only shows the content which the user is permittet to edit.
I there is a lot to do for such abig system but i would use this becouse i don't want to log on on each site with other username (security reasons i have vor each site diverent usernames and pass).
So i could change username and pass everyweek global and if there is a good module i wanna use more then one domain i could implement it global to all sites and so on.
Big projekts with diverent site(intranet use) could be so simple.

Please let use go for it.
Kishman

kishman155 wrote: I think it would be nice to have plugins and modules at one place and share it with other installations of CMSMS.

I see 2 issues here:

- security and AAA
When hosting CMSMS for other people the security issue could become serious when
having for example modules scripted with security relevant information like epayment
or other credentials for external services. It also become part of copyright, when having
a hosting party with his own modules which nobody else should have. This must be
resolved thru a sophiscated supermodule. Then its ok.

- memory footprint
As far as i can remember all plugins are loaded at loadtime. This will blow memory FP
when having all in one place. Also security and authentication issue could raise here.
Any ideas?

kishman155 wrote: A central config file for adodb wher it stored and an admin pannel for all would be nice but i think its very hard work to implement those thing.
The database must get splittet and the permissions had to say wich site content the user could administrate.
There had to be a filter which only shows the content which the user is permittet to edit.

Maybe it is possible to have a superpanel where a superadmin decides whether or not to let a the client admin
setup his own environment. Eigher have a predefined setup at the local host and database or let the client admin
decide if he wants to use for example another host or the database server. Since there is not real limit of virtual
databases of a database server like mysql, there is no need of having all in one place.

The client site content permissions should up to the client admin, also all other client site relevant
things also. I guess that is the simplest approach.

kishman155 wrote: I there is a lot to do for such abig system but i would use this becouse i don't want to log on on each site with other username (security reasons i have vor each site diverent usernames and pass).
So i could change username and pass everyweek global and if there is a good module i wanna use more then one domain i could implement it global to all sites and so on.
Big projekts with diverent site(intranet use) could be so simple.
Please let use go for it.

Authentication could also be layered. The releation could be:

a Client account is owner of N Client Site account(s). The Client is able to manage
N of client sites, distributing bulk permissions and modules .. etc. The questions is
what could be done with the available manpower of the current development team.

I guess to get a feeling of what is really necessary we (or i) have to check
out my proposed short run concept.

I'm very interested to hear from wishy what he thinks about the current proposes
and about what really could become real

take care

Michael

You are right koehler.

CMSMS overtop my wishes, hopes what would be done with 0.10 so i relax and code forward on my modules and look what wishy want to become real.

Have nice days like in holiday with CMSMS

Kris

lol, after all, we dont need lot's databases for lot's of cms's! one database with lot's of prefixes. ... one user on one comercial hosting have usually 1 database. Every virtual server will by have upload dir with for example database prefix name in upload subdirectory. But what will be with security? When "user f one server" can put into user tags code against another database, ergo db prefix.... or if one person will by admin for theses servers is no danger.

roman, yes you are right, the common single user installation do not need
high sophisticated installations nor even multi client capabilities. But what
we want to figure out in this discussion is: "how to multi client". If you do not
know what is the definiton of "multi client capability",  i may give you an idea:

For example Marvin Masters is running 3 Websites with CMSMS and someday
he decides to host another plenty installations of CMSMS for his friends or even
strangers who will help him paying the monthly traffic of his wrecked root server.

As long he is his own master and nobody else will have something do to with
his CMSMS's, he can mess around with modules, plugins and everything
else on his server. But when Marvin becomes a host for others, he have eigher
install plenty CMSMS in different directories or he may think about a multi client
capable CMS. Serious issues are with something like that.

Got my point ?


Michael

probably yes

roman, so what would you think about my security concerns
when sharing modules and plugins? Do yo may have an idea
what we could do to seperate the modules and plugins ?

Multi client capabilities Can by nice for upgrading CMSs , only one times... for everything. Bud with security, if y don't using separate databases for another virtual server, or separate tables, separate folders. Y don't can make secure this. I think. For Xoops exist multiclient modul, but i don't can find it now. Example in index. php file y will test whitch host is requested, and using case command get for CMS diferent config file....with diferent uploads directory, dbprefix etc. If somebody will like to take informations, or change something in another part of CMS(another site) he can do it... dprefix, and dirnames can by ~10 chars long...read config file as text file from part of site if y have permission read this fiel is no problem.

maybe this thread is what you are looking for:
http://forum.cmsmadesimple.org/index.ph ... 265.0.html