A dedi server is the same as using your pc, it uses remote desktop access.
The best advise i can give is that you learn as much as you can about mir, you must make a few choices first.
1. Will you use the svn files and code them, which will require a team of developers
2. Use TDs files or something else, which wouldn't require a server team but may help cut the work load.
In my experiance with 2.3 mir, the obvious choice is to use TDs files as they are the most sercure, stable files about atm, they are very flexable with how you can use them via complex and carefully planned scripting.
Also take these points into account when deciding if you'd like to have a dev team or not.
Pros:
1. Workload evenly distributed, so you can focus on what your task/s is/are and do it well.
2. The benefits of having the support of your team should you need it. *keep in mind that is also what LOMCN is here for too*
3. Following on from point 1, the overall quality of the server would benefit, only on the assumption your team are given the correct roles for their skills, such as a map maker shouldn't be given the task of scripting.
4. Going by point 2 in the Cons, you may find yourself in a position where you are unable to manage the server due to w/e reason and cannot work on the server and having a team to support the server in your absence would be an advantage.
Cons:
1. Finding a team that will offer what you need and not someone that thinks they're anygood, but is only after a gm position
2. Deadlines, if you and team are working toward a deadline for a patch and someone on the team is slacking it can cause alot of disruption, most of the time it you'll find personal matters get in the way and obviously they would take priority.
3. Make sure you check previous work of anyone you decide to join your team, this is a crutial part as you don't wish to have bugged scripting or half arsed patch work.
I've been running my server solo, since 1.4 for over 3 years now. Its been a tough job and wished i had got myself a team from the switch over to TDs 2.3 files. Its very hard todo it alone but atleast you have your standards and you know that anything that goes on the server will meet them.
If you plan on using TDs files, make sure you read the "update.doc" and the "if + act statements.doc", the better understanding you have of the server and the scripts the more you will get out of it.
G/L with your server
