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

Slashcode on Windows?

posted by Cliff on 06:22 PM June 26th, 2000   Printer-friendly   Email story
Faust asks: "Has anyone tried to get Slashdot to work in a Windows 9x or 2000 environment? If so, has anyone succeeded? I am not looking to use it for production, but rather to learn how to customize Slashdot before I fork over some money to SlashHosting. I doubt Slashdot can work with ActivePerl 5.6, but I noticed that Dynamic Perl is a binary build of Perl 5.6 for Win32 with an integrated Apache webserver and thought it might be able to work with that. I think Jeffrey Baker (of Apache::Session fame) may have done some work with mod_perl in a Windows NT environment, but I don't recall the details. I would be thankful for any guidance, even if it is just to give up and forget about it."
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
More | Login
Loading... please wait.
  • I understand your feelings, but I just can't see that the attitude is the real problem. The real problem often IS the OS, and if your OS is flawed in some significant way to make your work difficult, then, well, yes, get another OS. There is always a choice of OS. It's just that you aren't always the one making the choice.

    I'm not saying that the general attitude is the problem. What I meant was that that particular AC:s comment in effect of "Duh, use another OS, stupid!" was stupid because he didn't eve

  • by Anonymous Coward
    I know someone wrote slash in asp for windows but I do not recall the url. I do not think that they released the source code however. I could be mistaken.
  • by Anonymous Coward
    a "slash-like" program is located at www.wonko.com
  • by Anonymous Coward
    good luck getting everything to run. better off installing linux and getting down to business. by the time you port to windows, you could have installed the OS, needed apps, and gotten it up and running to verify you are smart enough.

    http://www.gosports.org [gosports.org]

  • by Anonymous Coward
    The "slash-like" code that runs wonko.com was not actually modelled after Slash, and is not a port, but it is very similar. It was recently released under the GPL. There's a SourceForge project for it here [sourceforge.net].
  • good luck getting everything to run. better off installing linux and getting down to business. by the time you port to windows, you could have installed the OS, needed apps, and gotten it up and running to verify you are smart enough.

    Huh? Sometimes anything but Windows is out of the question. Like in my case:
    I'm about to bring up an internal news site for a public hospital this summer and was looking at Slash - it has almost all of the features needed. But the problem is that this is an NT shop. Even if I'd love to put up a Linux box and install Slash on it, it's out of the question - because, by the time I leave, there will be absolutely no one around here that can maintain that box.

    I've fought with ActivePerl and Cygwin and Win32-MySQL here for days to make them work together and right now it obviously looks like I'll have to use something else than Slash. But that's not my point. The point is that some times there is no choice in the underlying platform and if that means that Slash won't run, there is a problem and the attitude "Duh, use another OS, stupid!" doesn't help at all, because it's out of the question.

    Right now, it clearly is my problem and the problem of everybody else that would like to run Slash on Windows for various reasons. But I think that it is somewhat of a problem also for Slash in the long run.

    Back to the topic: An AC pointed out the site www.wonko.com [wonko.com] and it appears to be running NovaShare [novashare.com] which seems to be a Slash clone ported to NT and MS SQL server and the whole thing, so maybe I'll have a look at it. But it's commercial and not open source, so I'm not completely happy with it.


  • by Anonymous Coward
    I would guess that the main problem would be getting mod_perl to run on windows - it can be done, I have done it, but it was a pain as of 4 months ago. You should check out perl.apache.org [apache.org] for more info.
  • It looks like Anonymous Coward is right.

    On Tuesday June 27, @04:41AM EDT, menthos [slashcode.com] (com.menthos@menthos) wrote:

    I've fought with ActivePerl [activestate.com] and Cygwin [cygnus.com] and Win32-MySQL [mysql.com] here for days to make them work together and right now it obviously looks like I'll have to use something else than Slash.

    On Tuesday June 27, @01:34PM EDT, Anonymous Coward wrote:

    I would guess that the main problem would be getting mod_perl to run on windows - it can be done, I have done it, but it was a pain as of 4 months ago.

    I think I tried one of Randy Kobes's old binary distributions [uwinnipeg.ca] (sans experimental fork emulation) back in December of 1999 to try out HTML::Mason [masonhq.com] and couldn't get everything to work. I doubt Kobes's binaries are an answer anyway since the SlashCode INSTALL DOC [slashcode.com] clearly states:

    You MUST install mod_perl and Apache as directed here. OK, that is not strictly true, but it is mostly true. If you already have mod_perl installed, chances are it is not configured properly to work with Slash and you must rebuild it. If you are using the provided httpd.conf file from the slash distribution, and Apache is giving you errors, chances are mod_perl is not installed correctly, and you need to build it from scratch.

    So, it looks like Anonymous Coward's advice carries the day. I won't waste my time trying to demo SlashCode in a Windows environment. But. instead of "installing Linux and getting down to business", I'll just fork some money over to SlashHosting [slashhosting.com], unless anyone knows of a better hosting solution.


  • The point is that some times there is no choice in the underlying platform and if that means that Slash won't run, there is a problem and the attitude "Duh, use another OS, stupid!" doesn't help at all, because it's out of the question.

    I understand your feelings, but I just can't see that the attitude is the real problem. The real problem often IS the OS, and if your OS is flawed in some significant way to make your work difficult, then, well, yes, get another OS. There is always a choice of OS. It's just that you aren't always the one making the choice.

    I'm not saying that people don't have bad attitudes sometime when saying to pick another OS. But if someone came to me and said they couldn't win the Grand Prix in a Yugo, I would advise them to get a different car. If they for some reason couldn't, then that is their cross to bear, but I would give them that advice all the same.

    Anyway, someday we might get Slash to work on Windows. It is a low priority, but it may happen.

  • by Anonymous Coward
    wow, this is an old thread, but i thought id point out that novashare [sourceforge.net] is open source now. http://sourceforge.net/projects/novashare/
  • sorry, i thought the point was that you wanted to learn something before you forked over cash and that you were only open to "learning" in windows. no problems now that i understand your scenario. be carefully with hospital information on a box not owned by the hospital. seriously.
  • So, it looks like Anonymous Coward's advice carries the day. I won't waste my time trying to demo SlashCode in a Windows environment. But. instead of "installing Linux and getting down to business", I'll just fork some money over to SlashHosting, unless anyone knows of a better hosting solution.
    That's your choice, but I agree with the AC who posted before that it might not be a good solution keeping critical data on someone elses system, especially when a hospital would probably be better served by something available on both the internet and the hospital's own intranet. Good luck with whatever choice you do decide to go with, however.

    On that note, though I would be interested to know exactly what parts of Slash were giving you the most grief. The ability to run Slash on a variety of platforms is a concern, albiet a minor concern at the moment.