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
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Slash installation in one step?

posted by Krow on 07:50 AM August 3rd, 2002   Printer-friendly   Email story
I think Slash installation is simple and clear, but also, it's manual.
There must would be an automatic installation procedure.

I'm thinking in a Perl script based on a response file or similar that installs Slash components (Apache, mod_perl, MySQL, Bundle::Slash and Slash itself) all in one step.

Of course, you have previously to wite the responses to interactive questions that will be formulated during installation process.
This response file may act as your 'Slash based settings for your site'. Also, the Perl script may write an 'installation log' during its execution.
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.
More | Login
Loading... please wait.
  • Why would that be something I want? Isn't that what .RPMs or BSD Ports are for? And don't most Unixes already pretty much default install MySQL?

    I can just see some "master script" foobaring my system. Perhaps overwriting my Apache configs. Or overwriting my MySQL install. And who is going to update this script? The slash guys? They STILL don't have the FreeBSD script for slashd right, it's still in the Bugs on sourceforge. It's been OVER a year [] on that one...

    No, I think the install for Slash is perfect. It's easy. Unbundle the source. Follow the directions and install all the necessary components (MySQL, Perl, Perl Modules). Make. Make install. It's all spelled out in the docs.

    I'd rather see time devoted to promised Plugins rather than easy install scripts. How about the Gallery Plugin? Done? The events plugin?


    It's either on the beat or off the beat, it's that easy.
    • The Events plugin is actually being used in places, so it is done for the most part.

      I was looking at the FreeBSD patches the other day and once again pushed them aside for the same two reasons:

      1) How close are they to the current dist?
      2) How do I test them?

      I don't have a freebsd box (want to send me an install CD? I might test it then). I don't even have a bootable image at this point of FreeBSD or I would test the patches against one of the blades in the house.

      Make a little more sense as to why they have never been applied?

      You can't grep a dead tree.
      • Hey, I'll give you mine CDs. Address?

        The only thing that is different is that it should look EXACTLY like the Linux one. The FreeBSD clause in the slashd gives errors. If it is exactly the same as the Linux line, it works fine. I can send you my script if you'd like.

        Hmm, the events works huh? I'll have to try it.....


        It's either on the beat or off the beat, it's that easy.
        • Email me directly for the address.

          Send me the latest of what you got for it (just email me directly).

          You can't grep a dead tree.
  • The biggest problem I had setting up Slash was getting all the makes to work. I must have had to play with 8-10 before I got everything to compile/install right. I think trying to put it all in one file is going to cause BIG problems.

    The longest bug I hit in the install was one or two of the SQL Perl modules not installing correctly in the Bundle. The trouble was that I didn't notice the errors in the pages of text the bundle install spewed out.

    I'm not saying that this couldn't be done well but it's going to take almost as long to write a decent (Key word) windoze style installer as it took to write Slash. There are too many fiddly bits. Just my 2c.