On Fri, 2006-03-17 at 11:19 -0500, David M Johnson wrote: > On Mar 16, 2006, at 9:33 AM, Henning Kulander wrote: > > What's needed here is a way to group "rolleruser"s and "website"s in > > domains so they can be controlled by domain administrators. The domain > > administrator also needs to be able to control default themes and > > available themes for one domain. (ie. blog.comany1.no has a default > > theme with the Company1-logo at the top, blog.company2.no has a > > different default theme, and the company1-theme is not available). > > > > One way to do this might be to add some extra tables to the database > > describing the domain. The table will contain name, description, > > domain > > settings etc. When a user is added to a domain, a connection between > > rolleruser and domain is created in a new table called domainuser. > > When > > a website is added to a domain, a connection between website and > > domain > > is created in a table called domainwebsite to show that a website is > > part of that domain (ie. a user can exist in more than one domain, and > > so can a website). The names of the tables are not final yet. > > > > The normal behavior in Roller should be left as it is now, but the > > administrator is given an option to turn on multidomain-mode. When > > this > > is enabled, the administrator can add new domains, and add an > > administrator-user to that domain. Existing websites and users will > > continue to exist as before under roller/page/sitename, what's new > > here > > is a new configuration where a domain administrator can add users, > > Are you sure you want to use pathinfo to partition domains? The > previous email seemed to indicate that you'd use (virtual?) domain > names to indicate different sites.
The reason for using pathinfo is to most easily fit into the existing model. URL-rewriting will then be used to map the virtual domains to paths in Roller. > > wesites and set configuration for the domain. This could be put under > > roller/domain/domainname for example. This level would also have > > functionality like the front page for roller, but would only contain > > blogs from this domain, a planet uniqe for this domain, and optionally > > the ability for a user to register for this domain only. (in the > > background, the user would also be registered as a global rolleruser, > > but the global site could be filtered out so this would be transparent > > for users). > > Sounds like the beginning of a reasonable plan. Note that we are > working on some proposals for changing the Roller URL structure (not > yet on wiki) and the way the front pages works. Do you have more info on that? > > What we need now is some feedback on what mistakes we are likely to > > make > > here, and how you would like us to proceed so we can get patches > > upstream and not break your incredible application. Ideas on how to do > > this would certainly help! > > I outlined a plan for doing this in my response to Trygve. When we get access to the Wiki, we will put up a proposal there. We are getting valuable feedback here that we will use in the proposal. Currently I am doing some experiments with the code to see if this will work. -- Regards, Henning Kulander System consultant Linpro AS - Norway's #1 Linux company
