multisite

Drupal ofrece la posibilidad de crear varios dominios administrandolos de manera centralizada.

Si su organizacion cuenta con dos marcos de trabajo separados, orientados a comunidades diferentes, pero necesitan ser administrados de manera conjunta, podemos llevar adelante dos sitios independientes con una sola instalacion, ejemplo
1. www.trabajo1.com.ar
2. www.trabajo2.com.ar .

1. ingresa a Panel de control del sitio, www.trabajo1.com.ar/cpanel

I would just like to inform/promote a site that I have worked on for the Sustainable Living Foundation. It is still a work in progress after nearly 2 years of involvement. Now, I have not spent all that time on this site and have built about 15 other sites in this time with drupal among other things. This site started with drupal 4.6 and has made it to 4.7.4. I can't remember all the modules I have utilised or trialed in this period along with two whole themes developments. The theme is shared across all six proposed multi sites but has a specific style file for each site.

Is there any general consensus on the limitations of a true multisite configuration?

I'm thinking about hosting quite a few sites on one shared host. The sites I want to run are mostly going to be low/medium usage which I would suspect would easily run on a single shared unit under normal circumstances. The plan is to use individual databases with a shared codebase running D5. I'm looking to find out what people think/know about the general limitations on numbers of sites, and numbers of modules in this setup.

Here's a few links to some info over at Drupal.org in the Installation and Configuration section of the handbook that might help you get started or identify an issue you may be having with your install. As I come across more of them, I'll add them to the list!

• Installing multi-site setup
• A drupal multi-domain module at last! (for RC5)

Has anyone successfully implemented og where each group lives on its own subdomain, but on a shared code base? We are looking at this as an alternative to a multi-site (separarate dbs w/ shared users) implementation. The wrinkle on this project is that the site could grow to a couple hundred subdomains. They don't need to be added on-the-fly via admin interface.

Any suggested approaches to this?

Is there a roadmap anyone might suggest for feature enhancements or supporting module development we might consider for the og module package itself?

(If 5.0 beta proceeds well, we'll likely be wanting to build this in 5.0 as well.)

My name is Mack Hardy, I am the technology manager for a non-profit called Post Carbon Institute.

Post Carbon Institute is running OG for its Relocalization Network (http://www.relocalize.net/grouplist). We all need communication tools to organize, only when we are organized can we be effective. We want to enhance og2list so that our users can choose to use email as the primary interface to other people in their groups. OG2List is promsing, but has a couple outstanding features which we are going to fund further development of.

The scope of the next stint of work will be:

I had converted the xmlrpc library to Jsolait XMLRPC. This library provide a much more intituive way to make XMLRPC calls and also provide a good way to implement Module and Class. However, the classes and modules wrapper can slow down debugging process as it prevent showing source code line numbers in the error console.

I also create a multisite manager. With multisite enable we can administrate multiple sites concurrently. The login screen has been removed and replaced by a sites manager screen - where you can add or remove sites to be managed.

Here is a screenshot