By Mateo1041 on

In the past we've used name-based virtual hosting in Apache for Drupal websites. We recently converted websites to SSL and had to go the ip-based route. As a result, we currently have an instance that is set up as follows:

* www.domain.com using port 80
* dev.domain.com using port 8080

Both use the same IP. Is this scenario possible using Drupal multi-site functionality? While we find that dev.domain.com works and reads the correct "dev" database (using the dev settings), it reads theme files from the "www" site instead which is not what we want.

Is the culprit the dev's htaccess file? Apache is listening on 8080 and does use the proper DB settings, but just not the correct theme files. One other note: browsing dev.domain.com:8080 gives an error: "The page isn't redirecting properly". Should we just purchase a new IP address for the dev website, or would this still not help?

Any advice would be appreciated. Thanks.

⋅ Categories: Drupal 6.x

Comments

schnippy’s picture

schnippy commented

I've got a number of multi-site installations setup using the same configuration you describe here so it is definitely possible with Drupal.

Do you have a separate themes folder for each of these instances? It should look something like this:

- sites
	-- all
		-- modules (shared)
		-- themes (shared)
	-- www.yoursite.com
		settings.php
	-- dev.yoursite.com
		-- modules (only ones in dev / staging release)
		-- themes (your dev themes)
Mateo1041’s picture

Mateo1041 commented

Yes, that's similar to what we have set up for multiple sites. If using port 8080 for dev.domain.com, would we need to do anything special in our settings.php file, .htaccess file, or sites/domain naming scheme? The strange thing is that the development website does pull the correct DB data (different DB than production), but not theme files.