By saltcod on

Hey All,

Wondering about how to do multisite with install profiles. For my other sites, I've got a normal d6 codebase at /root, with subdomains in /sites. Like so: 

document root 
	sites/all
	sites/default
   	sites/sub.example.com
  	sites/sub2.example.com
  	sites/sub3.example.com

etc...

To run something like Open Atrium or Open Publish or Managing News,would I need to have a new vhost setup?

So, something like: 

document root
	
	d6
		sites/sub1.ex.com
		sites/sub2.ex.com
		sites/sub2.ex.com
	open atrium
		sites/atrium1.ex.com
		sites/atrium2.ex.com

etc...

I guess what I'm really asking is: can I run 'normal' d6 and an install profile from the same codebase? And have: 

document root
	sites/d6-1.ex.com
	sites/d6-2.ex.com
	sites/atrium1.ex.com
	sites/atrium2.ex.com
⋅ Categories: Drupal 6.x

Comments

picxelplay’s picture

picxelplay commented

If you are still watching this post, and for anyone else; Don't mix Open Atrium and a regular d6 in a multisite. OA uses/can use different patches than regular d6.

GOOD:
[MultiSite Install A - Core Codebase A]
sites/d6-1.ex.com
sites/d6-2.ex.com
sites/d6-3.ex.com
sites/d6-4.ex.com
[MultiSite Install A END]

GOOD:
[MultiSite Install B - Core Codebase B]
sites/atrium-1.ex.com
sites/atrium-2.ex.com
sites/atrium-3.ex.com
sites/atrium-4.ex.com
[MultiSite Install B END]

BAD:
[MultiSite Install C - Core Codebase C]
sites/d6-1.ex.com
sites/atrium-2.ex.com
sites/d6-3.ex.com
sites/atrium-4.ex.com
[MultiSite Install A END]

----
Sudo Kill Cylons

picxelplay’s picture

picxelplay commented

Let me add to my answer.

Technically it is possible, but I would not recommend it unless you really know what you are doing and you really need to do this. You have to be very careful what exact versions of what are in sites/all/modules, sites/openatrium/modules, and in the open atrium install profile. I wouldn't recommend it for the regular user.

----
Sudo Kill Cylons

francewhoa’s picture

francewhoa
he/him
Primary language French
Location Sept-Îles, Québec, 🇨🇦
commented

I agree with picxelplay. Unless you consider yourself having advanced Drupal & Open Atrium multisite skills I would not recommend [MultiSite Install C - Core Codebase C]. We tested [MultiSite Install C - Core Codebase C]. It works. But it's a nightmare to maintain. Mostly because you have to keep trac of all module versions. In other words, ensure your Drupal multisite and Atrium uses the same contrib modules version. And there are a few risks to consider. For example if you install the same module twice or one of the module version doesn't match both multisite install then you risk braking your database, get error messages, and possibly data lost.

Loving back your Drupal community result in multiple benefits for you  
francewhoa’s picture

francewhoa
he/him
Primary language French
Location Sept-Îles, Québec, 🇨🇦
commented

Confirming [MultiSite Install B - Core Codebase B] works

Loving back your Drupal community result in multiple benefits for you  
saltcod’s picture

saltcod commented

This is an old thread that was revived a few days ago. As the original poster, I feel compelled to respond with my experience over the past few months:

After starting a pile of new projects as multisite, and converting a pile of old ones, I ended up switching back to single codebase installs. Multisite (at least for me) has been a complete nightmare. Instead of developing new ideas and making new sites, I was spending all of my limited time trying to fix the old sites.

If you're coming to this thread looking for advice on multisite setups: don't do it. Have a new document root, a fresh codebase, and fresh modules for all of your installs. You'll be thankful for it later.

(obviously not meant to bash the multisite feature, it just takes time and effort to maintain, and I'd say that this effort isn't necessarily warranted for the benefits you gain.

Terry

gnucifer’s picture

gnucifer commented

On the other hand, I work at a company with 100+ sites on same multisite sharing 95% of modules. And it works well as long as you perform updates regularly and have some kind of staging process with a testing and production environment. We could never be as cost affective without the multisite feature because we a) Only have to update modules and core once for all of our clients. b) Can use APC very efficiently. We are using 500-600 mb for APC right now, would not dare to speculate how much that would be if we had one drupal core and module repository for each site.

Maintenance hell for us happens when running serveral different cores, like for different installation profiles, or maintaining the sites local modules. The multisite feature IMHO is one of Drupals biggest selling points.

merovech’s picture

merovech commented

Could you maybe give an outline of how your VirtualHost configuration was done? I'm trying to set up Open Atrium on a codebase separate from my Drupal multisite setup's codebase. I currently have VirtualHost entries for each Drupal site (example1.localhost, example2.localhost) in my Apache configuration.

My question is, if I untar OpenAtrium to /usr/share/atrium, how do I modify my Apache VirtualHost configuration? Let's assume I want to "serve" OpenAtrium sites for web requests to atrium1.localhost and atrium2.localhost.

This is the current /etc/apache2/sites-available/default configuration:

<VirtualHost *:80>
	ServerAdmin someone@example.com
	DocumentRoot /usr/share/drupal6/
	ServerName example1.localhost
	RewriteEngine On
	RewriteOptions inherit
</VirtualHost>

<VirtualHost *:80>
	ServerAdmin someone@example.com
	DocumentRoot /usr/share/drupal6/
	ServerName example2.localhost
	RewriteEngine On
	RewriteOptions inherit
</VirtualHost>