Mat Schaffer on 13 Aug 2007 19:21:48 -0000

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PhillyOnRails] couple simple ror questions

  • From: Mat Schaffer <>
  • To:
  • Subject: Re: [PhillyOnRails] couple simple ror questions
  • Date: Mon, 13 Aug 2007 15:21:29 -0400
  • Dkim-signature: a=rsa-sha1; c=relaxed/relaxed;; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=ntH/bhTG4p09ScKOerFyug5N1PZ/4Jdx7GZyYLJy2wDlOLSvQQlqv766SWJxJi19ONna+XWrAiVPOXb2O18LFEeOScr5B0ClJF9DscbU4j9nHjKfqWy7WJo52JdpgN+W2ncFMw1vxVF4L+60lQiQ+ImPhYJVsp1ZCfUQkrcMsbk=
  • List-archive: <>
  • Reply-to:
  • Sender:

On Aug 13, 2007, at 1:10 PM, Keith Fitzgerald wrote:

agreed about documentation but i can't help to think about Martin Fowler's paper on continuous integration:

"The basic rule of thumb is that you should be able to walk up to the project with a virgin machine, do a checkout, and be able to fully build the system. Only a minimal amount of things should be on the virgin machine - usually things that are large, complicated to install, and stable. An operating system, Java development environment, or base database system are typical examples."

Although we don't build ror apps, I feel like this is still sound advice. We should be able to deploy onto virgin machines.

As ror continues to grow [and libraries continue to expand], i can't help but think that the documentation solution will become a bit unwieldy.

Plus, as a developer what would you rather: you checkout and *it just works* or you checkout and spend the next 30 minutes or so reading documentation [which very well might not be totally up to date]

Yeah, docs do get unwieldy. The install to virgin machine thing is totally doable via rake, but if you're dealing with someone else's app they might not have thought to build in rake tasks to do things like look for and install dependencies. I bet you could even work out a method to let gem handle the dependencies directly. Possible a gem spec for your rails app or something.

But how many developers really take the time for that sort of infrastructure on a webapp? Not many in my experience. I feel thankful to get unit tests and decent code coverage.

To unsubscribe or change your settings, visit: