From: George T. <geo...@gm...> - 2011-02-06 12:51:14
|
So I've made two attempts to install Slashcode on a virtualized server. I can install any number of different distros. I've tried CentOS 5.5 and Fedora 14, and crucial functionality seems to be missing by the time I get done with Slash. (In the former case, I couldn't see how to post comments; in the latter, I couldn't post comments or stories, or manage users.) My ability to manage an install is not strong. I may be making bonehead mistakes. Or I may be using components that are too new. Before I conclude that's a matter of PEBCAK, let me ask those who are still here: The last time you successfully installed Slashcode so that it was up and fully functional, what distro did you use, and what versions of Perl, MySQL, Apache and...well, Slash? Was it actually 2.2.6, or was it something from the repo? For starters, I can tell you that on my second effort, it was Fedora 14, Perl 5.12.3, MySQL 5.something, Apache 1.3.42, and Slash 2.52. Anyone see any red flags? We shouldn't expect anyone to want to use or support Slashcode when the documentation to install it is half-missing. I'd like to figure out what the latest of everything that work together for any given Linux distro. I volunteer to write that documentation. I could use your help. Hey, how about let's start with: what are the specs of what Slashdot itself is using right now? == George |