Re: [racket-dev] call for ideas
An addition to my earlier post: We're shifting to using Chef (opscode.com) for deployment to all our production servers. Chef works like this: - you write recipes, which specify how to install and configure a particular service (e.g. Racket) - for each type of machine you specify the recipes it includes - you tell Chef to deploy recipes to machines. It does all the remote access and fiddling around Combine this with VMs in the cloud and it makes sys admin *vastly* easier. You take a base image that consists of Linux distro + chef client, then run Chef to turn it into whatever type of machine you want. You can add new machines in < 1 min of user time (though the install typically takes ~10mins or more you don't need to be around for that). Hope that makes sense. I can explain in more detail. N. On Wed, Feb 9, 2011 at 2:45 AM, Matthias Felleisen wrote: > > > Dear Developers, we need ideas and input. ... _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] call for ideas
On Wed, Feb 9, 2011 at 2:45 AM, Matthias Felleisen wrote: > We have decided to reorganize the systems maintenance tasks over the > next few months. Part of the goal is to modernize, and part of the goal > is to give Eli more time for real projects. Good plan. > - DNS What's there to do? If I fiddle with our DNS setting once a year that's a lot. > - web pages We use Bytemark's Symbiosis (http://www.bytemark.co.uk/hosting/symbiosis) on our machine for hosting simple sites. It has simple config and auto-updates with security updates. > - mailing lists Google groups. Life is too short to mess around with email :) > - source repository Github. It has this system to hook into commits: http://help.github.com/post-receive-hooks/ > - bug reporting Kahu (http://www.getkahu.com/) It is written in Racket. :) [If you seriously consider this, we'll set you up with demo accounts. Kahu is billed as helpdesk (= bug tracking) and resource management so it isn't a perfect fit.] There are many other bug tracking systems. > - @racket-lang.org mail addresses Google. N. _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
[racket-dev] call for ideas
Dear Developers, we need ideas and input. We have decided to reorganize the systems maintenance tasks over the next few months. Part of the goal is to modernize, and part of the goal is to give Eli more time for real projects. Our first stage should involve "outsourcing" various services, where someone else maintains a hardware and software installation, and we just maintain the content. That outsourcing will include - DNS - web pages - mailing lists - source repository - bug reporting - @racket-lang.org mail addresses These services might all go to the same machine, or we might outsource them to multiple places. For example, "@racket-lang.org" mail is mostly handled by Google Apps, and maybe that doesn't need to change. As another example, github is an obvious home for the source repository, but it might not be so easy to get push information to DrDr. Any advice on this first step of reorganization? We hope to get the ball rolling by March -- Matthias _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
