I'm focusing on a little project having a couple of buddies and want to setup a server to operate our tools. I looked around at located solutions like Unfuddle however they don't give a CI server.
I'm now thinking about purchasing a Linode and running the next onto it:
I'm a Linux server newbie, the same is true anybody have writeups, advice etc relating to this? I know of Buildix, however they don't supply the combination I want.
I am unsure just how much energy you'll need, but what I have done previously is snapped up a classic pc. Easily wiped the hard disk and installed a suitable OS after which loaded my tools on that.
I setup port sending on my small router to transmit incoming demands into it. And I received my hands an engaged Ip URL (you will find free and pay-for your) and setup tools to always update the present Ip about the URL.
It labored great, was cheap and that i many userful stuff here about server administration.
Yes, setup is harder also it takes longer but when you take this task for 12 several weeks and you're simply having to pay (say $30 per month) then you definitely may well avoid $360 plus you acquired a great deal of insight directly into Admin-ing Linux(or even the OS of your liking).
I'd strongly advise against making use of your build server (presuming that you want to rely on it instead of it as being a "toy" or "experiment") as the introduction to an alternative OS platform. You're most likely to have the ability to personally support every factor of that machine's construction and operation, or you have to have the ability to hands them back to someone whom you can rely on to get it done for you personally.
Therefore, if you're comfortable just with Home windows, build it on Home windows. If you're able to, construct it yourself and ensure that it stays near to home. Avoid using a located solution unless of course you truly need so that it is available on the internet.
After you have your build server working well, and also have some comfort together with your capability to operate and support it, THEN consider creating another such server utilizing an OS or tools which are a new comer to you. You'll then have the ability to assess both build servers, and you'll also have a functional build server when things go wrong in your "experimental" one.
If, however, you do this being an experiment instead of for "production" use, i quickly would still recommend against getting it located (again using the caveat which you may have to share it on the internet)--ensure that it stays close and become familiar with it thoroughly (oh, beeeehave!).
Quite simply, if it's an "experiment", then do not let any obstacle for your freedom to experiment: not distance, not money, not discussing, etc.
For those who have Ruby installed, you are able to pull lower the deprec jewel ("deprec" is perfect for "deploy recipe", not "deprecated"). It's targeted toward Rails, but sets up Trac and source control and allow you to perform other admin tasks. It might be appropriate for your needs, but I'd counsel you to take a look.
Obviously, selecting a distro having a robust package management system can help with setting up commodity stuff.
For mail, I am unsure why you'd decide to run your personal, when Google is going to do it for you personally free of charge. (Exception: In case your application needs intimate use of mail, it may be better to run your personal.)