准备开发工具机
我正在与几个朋友一起开发一个小项目，需要设置一个服务器来运行我们的工具。 我查看了诸如 Unfuddle 之类的托管解决方案，但它们不提供 CI 服务器。
我现在正在考虑购买 Linode 并在其上运行以下命令：
- Mail : Apache JAMES
- CI：Hudson
- Wiki/Tracker：Trac
- 项目管理：Mingle
- VCS：SVN
我是一名 Linux 服务器新手，所以有人对此有任何文章、建议等吗？ 我知道 Buildix，但他们没有提供我需要的组合。
I am working on a small project with a few friends and need to set up a server to run our tools. I looked around at hosted solutions like Unfuddle but they don't provide a CI server.
I am now considering buying a Linode and running the following on it:
- Mail : Apache JAMES
- CI : Hudson
- Wiki/Tracker : Trac
- Project Management: Mingle
- VCS : SVN
I am a Linux server newbie, so does anyone have any writeups, advice etc about this? I am aware of Buildix, but they don't provide the combination I need.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果你安装了 Ruby，你可以下载 deprec gem （“deprec”是为“部署配方”，而不是“已弃用”）。 它面向 Rails，但会设置 Trac 和源代码控制，并让您执行其他管理任务。 它可能适合也可能不适合您的需求，但我建议您检查一下。
当然，选择具有强大的包管理系统的发行版将有助于安装商品。
至于邮件，我不确定您为什么选择运行自己的邮件，当 Google 将免费为您完成此操作。 （例外：如果您的应用程序需要密切访问邮件，那么运行您自己的应用程序可能会更简单。）
If you have Ruby installed, you can pull down the deprec gem ("deprec" is for "deploy recipe", not "deprecated"). It's geared toward Rails, but will set up Trac and source control and let you perform other admin tasks. It may or may not be suitable to your needs, but I'd advise you to check it out.
Of course, choosing a distro with a robust package management system will help with installing commodity stuff.
As for mail, I'm not sure why you'd choose to run your own, when Google will do it for you for free. (Exception: If your app needs intimate access to mail, it might be simpler to run your own.)
我强烈建议不要使用构建服务器（假设您打算依赖它而不是它作为“玩具”或“实验”）作为新操作系统平台的介绍。 您很可能需要能够亲自支持该机器的构造和操作的各个方面，或者您需要能够将其交给您可以信任的人来为您做这件事。
因此，如果您只熟悉 Windows，那么就在 Windows 上构建它。 如果可以的话，自己建造并放在离家较近的地方。 除非您确实需要通过 Internet 访问托管解决方案，否则请勿使用托管解决方案。
一旦您的构建服务器运行良好，并且对操作和支持它的能力感到满意，那么请考虑使用您不熟悉的操作系统或工具构建另一个此类服务器。 然后，您将能够比较和对比两个构建服务器，并且当您的“实验”服务器出现问题时，您将始终拥有一台可用的构建服务器。
另一方面，如果您将其作为实验而不是“生产”使用，那么我仍然建议不要托管它（再次警告您可能需要通过互联网共享它） - 保留它关闭并深入了解它（哦，beeehave！）。
换句话说，如果这是一个“实验”，那么就不要让任何障碍阻碍你的实验自由：不是距离、不是金钱、不是分享等等。
并且，享受吧！
I would strongly advise against using your build server (assuming that you intend to depend on it rather than it being a "toy" or "experiment") as your introduction to a new OS platform. You are very likely to need to be able to personally support every aspect of that machine's construction and operation, or you need to be able to hand it off to someone whom you can trust to do it for you.
Therefore, if you are comfortable only with Windows, then build it on Windows. If you can, build it yourself and keep it close to home. Don't use a hosted solution unless you truly need it to be available over the Internet.
Once you have your build server working well, and have some comfort with your ability to operate and support it, THEN consider constructing another such server using an OS or tools that are new to you. You will then be able to compare and contrast the two build servers, and you will always have a working build server when things go awry on your "experimental" one.
If, on the other hand, you are doing this as an experiment rather than for "production" use, then I would still recommend against having it hosted (again with the caveat that you might need to share it over the Internet)--keep it close and get to know it intimately (oh, beeeehave!).
In other words, if it is an "experiment", then don't allow any obstacle to your freedom to experiment: not distance, not money, not sharing, etc.
And, enjoy!!!
我不确定你需要多少电量，但我过去所做的就是拿起一台旧台式电脑。 擦除硬盘驱动器并安装适当的操作系统，然后在其上加载我的工具。
我在路由器上设置端口转发以向其发送传入请求。 我得到了一个动态 IP 地址 URL（有免费的和付费的）和设置工具来始终更新 URL 上的当前 IP 地址。
它工作得很好，很便宜，而且我学到了很多关于服务器管理的知识。
是的，设置比较困难并且需要更长的时间，但是如果您运行这个项目 12 个月并且您付费（比如每月 30 美元），那么您可以节省 360 美元，此外您还获得了对管理 Linux（或您选择的操作系统）。
最好的问候，
坦率
I'm not sure how much power you need, but what I've done in the past is grabbed an old desktop computer. Wiped the hard drive and installed an appropriate OS and then loaded my tools on that.
I setup port forwarding on my router to send incoming requests to it. And I got my hands a dynamic IP address URL (there are free and pay-for ones) and setup tools to always update the current IP address on the URL.
It worked great, was cheap and I learned a lot about server administration.
Yes, setup is harder and it takes longer but if you run this project for 12 months and you are paying (say $30 a month) then you save yourself $360 plus you gained a whole lot of insight in to Admin-ing Linux(or the OS of your choice).
Best Regards,
Frank