What does it take to run your own server?

[devn00b]

I'm not trying to discourage you, i'm just saying that trying to get it working is 1/2 the learning experience and will help you know how to fix problems as they arise...that said, you need no programming experience, and is rather easy to do if you follow the directions

[techguy84]

The problem is, and the main reason we never did it back in the day was, if you cant figure out how to get it running, you really should not be running it. Your going to get bombed with every newb question x 1000.

Also used to be a rule, you make somthing like that YOU support it. =P

Fully agree with you there devn00b. I put up my wiki guide in hopes to help people out with some of the new components and my PM inbox went to the crapper. Id get about 4 or 5 support questions a day roughly when I just had the wiki guide. Since I put the PDF up with some of those screenines, I still get 4-5 questions aday, but they are mostly for things that are for outside the guide. I like helping people so I am okay with it, but If your not in the habit of answering questions right and left, it may not be the best thing to put out something that can allow people to point to you.

John, although I like the idea of a package for easy setup, like dev said, it will remove alot of the inner details that most people go through and in turn, when something dont work, they will have no idea where to start. Seeing questions like

"My login dont work and all the post talk about this XML file. Where is that at?"

Will get very aggetating after awhile. Its best to set it up peice by peice because it will vary between not only systems, but people as well. Similar to why you can hardly ever find pre-compile binaries for your linux distro from the makers. You have to make it by source because of the million varibles out there that could cause a issue. The best feature of doing it piece by piece is that people will have a greater knowledge of what all is going on. They will know what zone and world are. They will know how connections are made and what ports are being used.

I dont want to deter anybody, but its from my exp with the guide I wrote, and how I could possibly function if I knew squat about whatever I just installed.

The best part about a guide and not a package though is that if things get updated, the guide can still for the most part function as a base to setup a new server. If you do not update your package, it goes the way cave's did and just gets older adn older and older.

[John Adams]

Originally Posted by techguy84

Similar to why you can hardly ever find pre-compile binaries for your linux distro from the makers. You have to make it by source because of the million varibles out there that could cause a issue.

Actually, Windows having binaries vs Linux not has nothing to do with a learning curve. There's 1 Windows. There's a bajillion *NIX. So on this point, I disagree.