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
· Slash
· Slash
· LiveJournal
· server code
· More on
· Also by vroom

Slash on server running Livejournal?

posted by vroom on 08:35 PM July 23rd, 2003   Printer-friendly   Email story
Slash
Maybe this is the wrong venue to ask in, and I'm sorry if it is, but this question has been nagging me for about the past week or so. I have a personal server running Slackware 8 with a custom-compiled Apache 1.3.27 (with the appropriate mod_perl) and MySQL 4.0.13. This server is currently running the LiveJournal server code and works quite well at this. I'm interested in attempting to set up slash for personal use (the Livejournal code is running for personal use as well), and herein lies the question. Can slash be run on the same server in another VirtualHost without having a separate apache installation/process and doing some fancy trick with mod_rewrite? Or am I asking too much? I will be happy to provide any further info anyone needs through e-mail (the e-mail link above is NOT spam-armored at all).
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.

Slash on server running Livejournal? 18 Comments More | Login /

 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • Sorry, I thought my e-mail address would show up as a link like on slashdot. Here's my e-mail address un spam-armored (please, don't spam/flame/etc. I get enough of that already): theseventhsage@1st.net [mailto]
    --
    Windows--The biggest beta test ever conducted
    • (please, don't spam/flame/etc. I get enough of that already)
      Maybe you should start to spam-armor your adress or be more careful with whom you share it with.
  • 1.3.27 has a major exploitable security flaw.
    --


    "How about you interface with my ass? By biting it!" --Bender
    • Security issues aren't a concern for me; the site will never be live on the net, and only four people will have access to the site, myself included. It's more a pet project, if you will. I'm just looking for a definite answer on whether or not I can run slash and livejournal simultaneously on the same instance of Apache, and if not, what sort of kludges or fancy tricks I have to perform to make it work.

      Also I'm interested in knowing if it's absolutely nevessary to run MySQL and Apache in GMT since it's a

      --
      Windows--The biggest beta test ever conducted
      • Well, I have yet to install LiveJournal, but it can't be too hard. I've seen Slash and Scoop run on the same box, and I have mod_php on all of my servers to do other things (like phpMyAdmin, our hosting business home page, etc) so I can't imagine that it cannot be done.

        If you don't care that the times will look wierd, just set them the same and forget about it - just don't make them different...
        --


        "How about you interface with my ass? By biting it!" --Bender
        • LiveJounal is actually pretty easy to install. The only catch with LJ is that only one instance of LJ can run per instance of Apache (i.e. you need a separate apache installation listening on another port to have multiple LJ installs on the same server). You just use two httpd.conf directives and the rest of the configuration is done by changing specified values in a perl script (farily well-documented between the script itself and the instructions available on livejournal.com). I think I'll try setting
          --
          Windows--The biggest beta test ever conducted
          • Well, that's fairly generic, but I can't see anything there that says "Slash can't be made to work with this."

            Let us know. Should be interesting to try and make it work.
            --


            "How about you interface with my ass? By biting it!" --Bender
            • I got it working. I was going nuts until I realized I needed to use "slash.$DOMAINNAME" instead of just "slash" (I kept getting the index page from the first virtualhost in httpd.conf). Overall there weren't many problems with the install (besides having to force the Apache::Cookie module to install).

              There was one minor issue. When I did make install for slash, I gave INIT=/etc/rc.d, which is correct. The slash script wasn't installed. I had to create /etc/init.d and rerun make install so that the scri

              --
              Windows--The biggest beta test ever conducted
              • Bad juju.

                I keep all LOCALLY generated init scritps in /usr/local/etc/rc.d

                I'm using FreeBSD, YMMV.
                --


                "How about you interface with my ass? By biting it!" --Bender
                • Matter of personal preference, I suppose. I usually keep all mine in /etc/rc.d/local and keep all daemons in /daemons. Unusual, I know, but it helps me with organization and backups.
                  --
                  Windows--The biggest beta test ever conducted
            • I did discover a problem this morning, a potentially crippling one. I can't create a new user or even log in. Every time I try, apache returns a 500 Internal Server Error. Somehow the login request for my first author account (slash) must have worked, though, because I'm getting the "This page was generated by ... for slash (2)" header above the two default stories, even though when I click on slash, to go to his user info page, I get another 500 Internal Server error. Further invesitgation shows the pr
              --
              Windows--The biggest beta test ever conducted
              • Logs are your best friend...
                --


                "How about you interface with my ass? By biting it!" --Bender
                • Yeah, I noticed. I had checked the logs and didn't see anything because my log rotate script had rotated the logs. When I realized that, I looked at the old log and discovered the problem. I didn't install Bundle::Slash through CPAN, I used the tarball from the Sourceforge project site and therefore didn't install all the required modules. Fired up CPAN and installed the modules that were being complained about and everything works now.
                  --
                  Windows--The biggest beta test ever conducted
  • The fact that livejournal is already running is pretty irrelevant. The only thing it proves is that apache and perl are currently configured properly. You have a working web server. That's not a bad place to start really. Slash requires more third party modules than livejournal. This means it takes a little longer to get going, but some of us obviously think it's worth it. Yes, you can setup livejournal in one vhost and slash in another and they won't destroy each other. I haven't done this myself ad
    • Yeah, that's what I figured. I just have no experiance with it personally.
      --


      "How about you interface with my ass? By biting it!" --Bender
    • I did have to recompile mod_perl and apache (I like mod_perl compiled in statically) because not all the mod_perl options slash needs were activated. It wasn't too much of a pain though. I may pitch this to my college as an easy way to do campus news updates. Install may be what they'd consider a pain but the end result would be worth it.
      --
      Windows--The biggest beta test ever conducted
    • I discovered a slight problem last night. When you install slash, it writes a main file with httpd.conf directives in it. These directives are all global. At least one of them, "AddHandler perl-script .pl" I suspect, interferes with Livejournal. I moved all these global directives into a separate file and Included it into the site-specific conf file (inside the virtualhost section), then restarted httpd, and everything works perfectly. If you ever install LiveJournal, be careful of that! I may get up
      --
      Windows--The biggest beta test ever conducted