Slashcode Log In
Making Slash Install Friendly?
Recently I was asked by a heavily trafficed website to investigate migrating their site to Slash. After downloading the latest codebase I'm reliving a lot of the installation frustrations experienced when I messed around with Slash over a year ago. I've installed lots of portals before like PhpBB, Nuke, MX-System etc. All of those installs were pain free. I'm writing to request that you guys simply the install process. How about some straight forward docs? I would suggest a list of required packages and then simple instructions how to get Slash working with Apache etc that comes with most distros.
Cliff adds: It's always a good thing when your software is fairly easy to install, but the problem with Slash is that it requires quite a few libraries and Perl modules to do its thing. Slash tries to simplify things as much as possible with CPAN bundles and the INSTALL file, but there's only so much the developers can do. Many times Apache+mod_perl will need to be compiled, and compiled properly, and this is where many Slash installs have problems -- the developers can't compile these things for you, so you end up having to do them, yourself.
Having said this, what ideas and suggestions do you have for the Slash developers? What things can they do now to simplify Slash installs. What things can they work on in the future to smooth over the pains installing Slash that you are experiencing, today?
Having said this, what ideas and suggestions do you have for the Slash developers? What things can they do now to simplify Slash installs. What things can they work on in the future to smooth over the pains installing Slash that you are experiencing, today?
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.
Debian packages!
(Score:1)( http://ursine.ca/ | | Last Journal: Wednesday March 24, @03:53PM )
One thing that would simplify
(Score:2)( http://www.lottadot.com/ | | Last Journal: Monday July 12, @05:44PM )
a) include the more recent perl, and httpd
b) get them to compile it properly, just as slash needs
c) comments in the INSTALL doc on how to get Slash to properly work with OSX 10.3, and comments on whether or not one should strip perl/httpd1.3 off OSX and install from src or... etc etc.
d) get the distro's to include all/more-of the perl modules that Slash needs.
While I don't agree with some of what the article's submitter says (installing's *not* that hard on Linux, IMHO, and it's not installing slash that's hard, it's installing perl and apache that's difficult, like Cliff mentions), Cliff hit it right on the the nose when he talked about Perl and Apache.
The thing is, there is *PLENTY* in the INSTALL file that talks about how to use CPAN. Really, there is. And there *never* used to be that much information in the INSTALL years ago. It used to be if you didn't know how to use CPAN, installing Slash was way more difficult. If you follow the tips in the install installing with CPAN makes things *so* much easier. Most of the perl modules do install on their own (again, Linux, Redhat9/8/7 referred to there).
For those of you that have been using Slash for a few years, do you remember the days before Bundle::Slash?? Now *that* was a PITA.
From spending my time on IRC and answering people's pleas for help, I estimate that 99% of all the people who say they are having problems installing HAVE NOT READ THE LATEST INSTALL FILE completely, and are NOT following it's directions.
If OSDN could lay it's leverage and get a-d done above, that would probably help people start using Slash across the board. All they'd have to do is d/l the src, and 'make install', setup DBIx::Password, add GMT to their MySQL, and the run install-slashsite to create a new site.
--
lottadot [lottadot.com]
Questions about system requirements
(Score:1)I am running Slash CVS tag R_2_3_0_113 on an Athlon 750mhz machine with 256MB of ram. Merely visiting a webpage where index.pl gets called shoots up the CPU to 70 or 80% and page loads seem slow. Getting new hardware isn't a major problem. I just want to make sure that I didn't do something dumb which could cause this. Are there any suggestions of how to improve performance or do I just need new hardware?
The Gentoo Linux build system
(Score:1)Install Slash For Dummies
(Score:1)A response to the question, and then my own Q.
(Score:1)As for my question
slash.iso ?
(Score:1)