Slashdot Mirror

← Back to Stories (view on slashdot.org)

How To Build an Openfire Chat Server On Debian 5

Posted by kdawson on from the take-aim-first dept.

palegray.net writes "Inspired by a recent Ask Slashdot, I've written a step-by-step tutorial for setting up an Openfire server on Debian Linux, for those interested in running their own open source collaboration server. Aimed at those just getting started with collaboration software, the tutorial shows precisely how to get Openfire up and running quickly on a base Debian install, and offers a basic feature tour of the software's plugin and IM gateway functionality."

3 of 108 comments (clear)

  1. How To's are so 90s.. by Anonymous Coward · · Score: 5, Interesting

    These days you make me a VMWare image I can just pop-in and run.

  2. For the rest of us... by geekmux · · Score: 5, Interesting

    Something this basic requires a posting on the front of Slashdot? Great choice, kdawson!

    I'll be sure to try and get my article about setting Openfire up on FreeBSD here soon..........

    Ah, feel free to excuse yourself at anytime if you feel the rest of us are not worthy of your all-knowing power.

    He was merely posting as a response to several queries he had received for the information, and since it's not quite as simple as apt-get to do this, along with the fact that FOSS collaboration tools are gaining popularity in this economy of ever-shrinking budgets, I find it rather relevant.

  3. Re:Finally... by fm6 · · Score: 5, Interesting

    Man pages are (or are meant to be) reference documentation. Reference docs are important, but yeah, so are procedural docs.

    Thing is, they're really hard to write well. I earn an absurd amount of money because I'm good at writing them. Most developers are not. Even the ones who are good writers (a distinct minority) tend to be good at academic-style writing, where you assume a lot of sophistication on the part of your reader. Such writers have no patience for the nit-picky detail good procedural docs need.

    (I once wrote software release notes which included an explanation of how to unzip an archive. The developers, who happened to be pretty brilliant computer scientists doing cutting-edge work, thought their audience was "smarter" than that and made me take it out. Wackiness ensued.)

    If you want good procedural documentation, you have to put a lot of work into creating it. Most open source projects don't have the extra bandwidth, and even if they do, they don't have people with the right skill set. That boils down to fluency with language and and stubborn patience when describing boring details. Not a big skill set, but one very few people seem to have.