"Making this architectural change simplified our development and deployment process. It also simplified the way we thought about the application. The only price we paid was loosing the ability to deploy the application to different web server without making changes. Fortunately, this price was purely hypothetical because we had absolutely no need nor desire to use a different web server in production. On the positive side, we were now hiding the fact that we were relying on Java Servlets to realise our web functionality. In fact, seeing what some of the other communities are building (e.g. Sinatra, Node.js, etc.), I'd be tempted to try to write a web application that doesn't use Servlets at all. Part of it for fun, part of it to overcome some of the limitations inherent with the Servlet model"

nice overview of three options today

"Once you’ve built your local branch the way you want (we advocate squashing and rebasing along the way to make code review easy), we’ve built a little command-line tool (soon to be open-sourced) called “lgtm” which enables you to open a new Pull Request from the command line: just type “./lgtm create” and give it a title.  If you’re fixing a bug, it’ll show you a list of your assigned bugs in our issue/workitem tracker, Pivotal Tracker, and automatically mark this Pull Request as a fix. (this way, Github & Pivotal’s automatic integration will resolve the bug in Pivotal once the fix gets merged)."

git push web

"At Yelp, we push new code live every day. Pushing daily allows us to quickly prototype new features and squash bugs in a proactive manner. Because we aim to deploy new code so often, we're always looking for ways to make the process efficient and painless. There are four main stages to the Yelp push process: code review, integration, testing, and finally, live deployment. Each step is important, and there are ways to maximize the efficiency of all of them."

Easily install common opensource software stacks

installing and configuring an automated infrastructure management system (puppet), version control system (subversion), continuous build and test (frequently cruisecontrol.rb), software deployment (capistrano), monitoring (currently evaluating Hyperic, Ze