Hi Devlist, I'm working with Green Media Toolshed to set up a system for managing multiple instances of Drupal on the same server and sharing information between them. We're very keen on sharing this and collaborating on it with anybody who's interested in something similar. I'm trying to figure out which of these functionalities are too specific to our use-case to be useful to others, and which the community would benefit from developing a standardized and well-supported way of doing. So, I've included a list of our target functionality below. Send feedback! Especially if you're interested in collaborating on this, or are working on something similar, or if you have ideas about how to implement it in a way that will be in-line with Drupal Core's future direction, or if you think it's crazy and can't be done. If there is enough interest, we'll set up a Drupal Group to coordinate. Cheers, =Tones= greenmediatoolshed.org tjones.cc ***** Green Media Toolshed Multi-Site Hosting Requirements Document, v0.3 Tim Jones - tim@tjones.cc - 19 July, 2006 1. Site management - Provide GMT admins with a "dashboard" list of all current GMT websites, including partner information. - Automatically deploy new Drupal sites based on site-template databases, via web interface. - Track database, client and domain data for all sites. - Allow and manage multiple domains/subdomains for each site. - Manage cron.php runs across all sites. - Run database queries across all sites simultaneously. - Manage and synch site filesystems. (I think this is only relevant if the setup it not using the Drupal "/sites/foo" convention.) 2. User / Client management - Users and clients have a many-to-one relationship. Clients and sites have a many-to-one relationship. - A user may log in to any site owned by that user's client. - Users have roles per-client that affect their permissions on client sub-sites. - Standard ("Authenticated") users are not shared between sites. (e.g. for Forums, Blog Comments, etc.) - Clearly the specifics of this need to be thought through more 3. API - Modules on a given site should be able to access contextual multihost information. For instance, - What client is this site for? - What other sites for this client are hosted on this system? - Any other relevant client/group data 4. For the Future: ("Wishlist") - Taxonomy sharing - Better mailing lists (possibly og2list?) - Multisite statistics aggregation - Other stuff?
There is something called Hostmaster, which is what Bryght.com uses for multi site. They are in the process of open sourcing it. There is also the sympal collection which is on drupal.org in the repository.
On 19-Jul-06, at 4:46 PM, Khalid B wrote:
There is something called Hostmaster, which is what Bryght.com uses for multi site. They are in the process of open sourcing it.
Not "in the process of" -- it is open source under the GPL. We have protected access to the repository at the moment. Contact me for access. The publish and subscribe modules may be a good solution for you. One can imagine a dashboard-style module that would have access to all the instances of a multi-site install for managing the cross-site integration of pub-sub. The XUL-based desktop admin client being developed as part of the SoC may also be appropriate for this purpose. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 SKYPE borismann http://www.bryght.com
Op donderdag 20 juli 2006 01:46, schreef Khalid B:
There is also the sympal collection which is on drupal.org in the repository.
chime. I am the maintainer of that[1]. Basically it is a PHP toolkit that a) already works but b) needs coding/fingers to clean it up. I have managed to tie it to both ISPconfig[2] and Dischosting[3] and I am confident that it is not hard to learn, if you are commandline savvy. If you want to learn "what it does right now" but more "what it should do in version 1.0" you should check out my blog on this [4] As for "but does it work?": Yes it does. I manage 40 (+2 new ones per month) sites with this, all over the commandline atm. Yes: it is a messy bit of tied-together scripts and yes it its far from release-ready. But sure: it has a clear goal and it is Free as in Freedom (gpl and accessible). Right now I am moving all the stuff into my own SVN, where I am integrating the scripts into a distribution (4.7+). You can follow progress in anon-checkout SVN: http://webschuur.com/svn/sympal/ Bèr [1] http://drupal.org/project/sympal_scripts [2] http://www.ispconfig.org/ [3] http://dischosting.sourceforge.net/ [4] http://webschuur.com/node/637 -- [ Bèr Kessels | Drupal services www.webschuur.com ] Paginas in je site bewerken: http://help.sympal.nl/paginas_in_je_site_bewerken
On Jul 19, 2006, at 3:39 PM, Tim Jones wrote:
Hi Devlist,
I'm working with Green Media Toolshed to set up a system for managing multiple instances of Drupal on the same server and sharing information between them.
We're very keen on sharing this and collaborating on it with anybody who's interested in something similar. I'm trying to figure out which of these functionalities are too specific to our use-case to be useful to others, and which the community would benefit from developing a standardized and well-supported way of doing.
So, I've included a list of our target functionality below. Send feedback! Especially if you're interested in collaborating on this, or are working on something similar, or if you have ideas about how to implement it in a way that will be in-line with Drupal Core's future direction, or if you think it's crazy and can't be done. If there is enough interest, we'll set up a Drupal Group to coordinate.
I outlined a summer of code project to do this and we had several submissions. I haven't seen any progress updates on the developer list about the SOC projects. You should check how that is working. Cheers, Kieran
Cheers, =Tones= greenmediatoolshed.org tjones.cc
***** Green Media Toolshed Multi-Site Hosting Requirements Document, v0.3 Tim Jones - tim@tjones.cc - 19 July, 2006
1. Site management - Provide GMT admins with a "dashboard" list of all current GMT websites, including partner information.
- Automatically deploy new Drupal sites based on site-template databases, via web interface.
- Track database, client and domain data for all sites.
- Allow and manage multiple domains/subdomains for each site.
- Manage cron.php runs across all sites.
- Run database queries across all sites simultaneously.
- Manage and synch site filesystems. (I think this is only relevant if the setup it not using the Drupal "/sites/foo" convention.)
2. User / Client management - Users and clients have a many-to-one relationship. Clients and sites have a many-to-one relationship.
- A user may log in to any site owned by that user's client.
- Users have roles per-client that affect their permissions on client sub-sites.
- Standard ("Authenticated") users are not shared between sites. (e.g. for Forums, Blog Comments, etc.)
- Clearly the specifics of this need to be thought through more
3. API - Modules on a given site should be able to access contextual multihost information. For instance, - What client is this site for? - What other sites for this client are hosted on this system? - Any other relevant client/group data
4. For the Future: ("Wishlist") - Taxonomy sharing - Better mailing lists (possibly og2list?) - Multisite statistics aggregation - Other stuff?
participants (5)
-
Boris Mann -
Bèr Kessels -
Khalid B -
Kieran Lal -
Tim Jones