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.
Full
Abbreviated
Hidden
Loading... please wait.



Debian packages! (Score:1)
Re:Debian packages! (Score:1)
Re:Debian packages! (Score:1)
One thing that would simplify (Score:2)
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
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 hardwar
Re:Questions about system requirements (Score:1)
I've asked that question several times, and that's about the same answer I've been getting. The main limiting factor seems to be RAM. I'm thinking of putting Apache and MySQL on separate (small) boxes, just because that's what I've got sitting around. Maybe that will help.
⇒ Constitutionally Correct [cpne.org] ⇐
The Gentoo Linux build system (Score:1)
Re:The Gentoo Linux build system (Score:1)
Not checking the defaults I slipped and hit the submit button. There should be line breaks in there but I can't find a way to edit posts.
-lee
Re:The Gentoo Linux build system (Score:2)
tf23
lottadot [lottadot.com]
Install Slash For Dummies (Score:1)
Re:Install Slash For Dummies (Score:1)
A response to the question, and then my own Q. (Score:1)
As for my question
Re:A response to the question, and then my own Q. (Score:1)
slash.iso ? (Score:1)