From: <pll...@la...> - 2003-03-12 17:24:00
|
Hi all, I've got a slash website running, but also have some non-slash stuff running on the same server. One of them, which is a wiki, is being interefered with by some of the statements in the conf file required by slash. Specifically, I've narrowed it down to these two statements: SlashVirtualUser slashadm PerlAccessHandler Slash::Apache::User Is there any way to limit the scope of these statements? Or, is there any way to prevent them from affecting a specific Directory or Location? The wiki runs out of /cgi-bin/, so is there any thing I can place in the Directory clause for the cgi-bin dir which would over-ride these two statements? Thanks, -- Seeya, Paul -- Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! |
From: George C. <ga...@sp...> - 2003-03-13 01:24:59
|
** Reply to message from pll...@la... on Wed, 12 Mar 2003 12:23:50 -0500 I'm successfully running Slash and TWiki on the same Apache server without any problems. I set up 2 virtual servers under two different host names on the same system. www. and twiki. Since the statements you referenced are in the site config file, they don't impact the other virtual server. I had to make one change to the site config from that generated by the install scripts - Change the VirtualHost statement from the hostname to the "*", and include the ServerName directive in the Virtual Host. #<VirtualHost www.sitename.org:80> <VirtualHost *> ServerAdmin ge...@si... ServerName www.sitename.org And for my twiki server <VirtualHost *> ServerAdmin ge...@si... DocumentRoot /usr/local/twiki ServerName twiki.sitename.org - I also added a redirect so that users could reference a particular twiki page by adding a twiki/ to my hostname. Redirect permanent /twiki http://twiki.sitename.org/twiki/bin/view/site/WebHome Mailman and modSurvey also coexist on this same server without any issues. George |
From: Alex M. <alex@OWAL.co.uk> - 2003-03-13 10:44:43
|
At 17:23 12/03/03, you wrote: >Hi all, > >I've got a slash website running, but also have some non-slash stuff >running on the same server. One of them, which is a wiki, is being >interefered with by some of the statements in the conf file required >by slash. Specifically, I've narrowed it down to these two >statements: > > SlashVirtualUser slashadm > PerlAccessHandler Slash::Apache::User I successfully have a public slash site on http://www.owal.co.uk/news/ and a private wiki which is also on the same site but in a different directory. Basically I avoided the problem you describe by putting my slash site in a sub directory. A previous poster put the slash site in a different Vhost. PS Anyone with news about professional open source support should submit it to my news slash site at http://www.owal.co.uk/news/submit.pl Such things of interest might be professional hosting of OSS, training, consultancy, support, etc.... I'm not interested in simply stuff which would appear on Freshmeat. Alex Available for java/perl/C++/web development in London, UK or nearby. Apache FOP, Cocoon, Turbine, Struts,XSL:FO, XML, Tomcat, JSP http://www.OWAL.co.uk/ |
From: <pll...@la...> - 2003-03-13 15:38:21
|
In a message dated: Wed, 12 Mar 2003 20:24:12 EST "George Clark" said: >** Reply to message from pll...@la... on Wed, 12 Mar 2003 >12:23:50 -0500 > >I'm successfully running Slash and TWiki on the same Apache server >without any problems. I set up 2 virtual servers under two different >host names on the same system. www. and twiki. Since the >statements you referenced are in the site config file, they don't impact >the other virtual server. Hmm, I had considered this. The only problem I have is that I don't have any access to the DNS servers, and therefore, to create multiple CNAME records pointing to the same host is a royal p.i.t.a. I had hoped for a solution where I could isolate that particular directory from the slash configuration. Though, I suppose this might be the easiest way. I guess I'll have to beg with the IT group to give me another DNS entry :) Thanks! -- Seeya, Paul -- Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! |