hello everybody
ife a littel problem. i wanna start with drupal 6 with the multiple domain structure on an debian/apache enviroment
i know i should make a top domain
lets say /var/www/maindomain/
and put herethe drupal files and for subdomains i should use the sites directory like
/var/www/maindomain/sites/subsite
so here is my problem, this structure is only barley useable for me
i still have running many sites like
/var/www/....
here i have an suooprt, domain 1, domain 2 etc like
/var/www/support
/var/www/domain1
/var/www/domain2
and so on
problem ist changing them su an subdirectory is a bad thing for me. manythings on our server pointing directly to the subdirs.
also the hole vhost conf, sitestatisticsoutput (3 differnt analyze progs for some other users) and so on
so i really dont wanna change now the hole structure to use drupal
is it useable to put siple symbolic links to the /sites directory ?
lets say ife drupal in
/var/www/drupal (drupal.domain1.com)
and the other sites in
/var/www/www.domain1.com
/var/www/support.domain2.com
and simple make an simbolic link from /var/www/drupal/sites/symbollinkdomain1.com to
/var/www/www.domain1.com
and the vhost in apache also points to /var/www/www.domain1.com
isnt that a way to do it ?
second idea (additional to that one is)
install drupal in an secure admin aera like
/var/www/admin/drupal (where admin is secure by htaccess and or https) reachable by admin.domain1.com/drupal
and subdomains points from /var/www/admin/drupal/sites/domain2.com(symlink) to
/var/www/domain2.com (where also the chost points to)
possible?
anyproblems?
unuseable?
nobody tryed yet? (means if have to go the hard way to find out after 1 week that there will be a major problem and ife to resetup everything :-)
Comments
You can make drupal run from
You can make drupal run from anywhere underneath the web root directory.
So for your drupal6 you might have your layout be similar to:
/var/www/drupal6/sites/domain1.com or /var/www/drupal6/sites/default
/var/www/drupal6/sites/domain2.com...
/var/www/drupal6/sites/domainn.com
with /var/www/drupal6 being the Drupal 6 install directory. You can replace drupal6 with whatever directory or directories you want.
In your vhosts.conf, have the DocumentRoot point to /var/www/drupal6 for the sites being served by Drupal.
uuhmmm
im sorry but that wasnt the question.
i know i can setup the main drupal whereever i want to and point the vhosts conf to that location (okok i should not to the /dev:-)
not he problem is
first i dont want to change the existing directory structure for many many reasons (beginning from permissions ending with existing content and followed by daily produced statistics for many websites) i dont want to reconfigure everything.
second its not possible to set every vhost to the same directory because some of them are https some not
some of them are htaccess secured some of them not... so its a wild mix and drupal should make now the content on that ;-)
but now (after hours) i found a way
http://justinhileman.info/blog/2007/06/a-more-secure-drupal-multisite-in...
describet exactly the way to do what i wanted to
here you can define for every site his own extra directory (with all features like htacess, https, own robots)
and also your fireld on site1 (lets say site1.com/member1/statistics/) isnt accessible at site2.com
great documention this guy made thanks to him... answered all questions (and i pray it will work *lol*).. i will test it tomorow
for other interrested users :
with that solution
youll have /var/www/drupal (without any domain pointing to)
/var/www/site1.com
/var/www/site2.com
so all websites psyically in their own home just the drupal needed files point to the codebase (much more secure) and pretty flexible
PS: if that work out it should come to the documenation and a second recomented way for installation. the sort domain by drupal to right content method seem not only unsecure also not really professional and in future really problematical.
this method seems like the typo3 method wheres standart to have an extra codebase and an skeleton for the subsite
so thanks again to justin hileman
so the question is closed ... discussion about tha still welcome :-)
Sorry I misunderstood you.
Sorry I misunderstood you.
Yes, having each site run from its own Drupal code base works too. It's not the recommended way for handling multiple websites because of Drupal's multi-site capabilities.
and here we go
jup you did,.. no problem but thanks for trying to help me so fast :-) (my guess is my horrible bad english is the reason for the missunderstood :-)
but you should read the link i posted
the trick is by that way you have one codebase for all sites while all sites having their own home
drupal even dont know enything changed. for drpal its same like the normal installtion
and here i cannot understand the drupal way to handle that problem.
theres a reason why typo3 make it same way (skeleton and symlinks each website and hidden maincodebase)
1: the security issue by handly mutplesites by drupal
2: the problem with htacess secured and https secured sites (here you need a own drupal install again)
3: management of each individual site (ife youve more there than the drupal handled content like own directorys and extra files)
4: flexibility (with the solution i posted you can have one drupal mainbase for the hole server with the flexibility to have the vhost pointing to whatever you want to
5: every site can (und must have) his own robots.txt, etc
with that solution you can use the drupal multisite caps. without the downsides i described above
I read that article and am
I read that article and am wonderring if it gives that much advantage! I run 4 websites with Drupal's typical multiste installation, is it worth it to change my structure? I don't know! I wrote a post, and got a reply from a person that is way more drupal competent than me, he contributes to modules dev, he replied to my post :
''I remember that article and I had some reservations. A web-accessible symlink to a directory which is off the web bring that directory back in the web, so it seemed futile.''
Do you really think it's that more secure, there is still a .htaccess web accessible!! And with symlinks, isn't the settings.php also web accessible?