Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Installing Slash without rebuilding Apache

posted by Krow on 07:58 PM November 26th, 2000   Printer-friendly   Email story
stain writes "Is there a way to get slash running on a machine that already has apache installed on it. My problem is, that I can't persuade the admin of the server to rebuild apache for me. I played around with httpd.conf to get slash running, but wasn't successful. Has anyone ever done this?"

Does it have mod_perl compiled in correctly? If not, your SOL.

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • by Anonymous Coward
    Did you just add a Virtual Host directive into your httpd.conf with all of the slash site's specifics and the perl info in the example that comes with the slash release?
  • I just installed 1.0.9 of slash on redhat 7 with the redhat apache and mod_ssl rpm's. No recompile was necessary. I just had to install the perl modules and add the slash database to MySQL.
    When I changed my httpd.conf, I just created a and put all the configuration that was specific to slash in there so it does not affect any of the other 10 sites I'm running.
    If you want my config files, just e-mail me.
  • I detailed how to do it on FreeBSD in a similar question [slashcode.com] a couple of weeks ago.

    It's getting to be about time to make this a FAQ.

  • I had a similar experience. I have installed slash on a Redhat 6.0/6.1 machine via the rpm's and I have not seen any problems. Maby if I was made aware of the problems that people have had with rpm's I might be able to figure out what might not work but from what I have seen, everything does work. It seems like all that needs to be done is to install a DSO of mod_perl that has everything installed with it. Someone please correct me if I am wrong.
  • Exactly. I used the slash/httpd/vhosts.httpd.conf file since it was more modular than the other conf file.
    The nice thing about containing everything in a virtualhost was that I didn't have to worry about ruining other sites on my server.