|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PhillyOnRails] couple simple ror questions
|
perhaps we could "document" your dependencies in a rake task that attempts to do a gem check, and if it doesnt work out for any reason, first attempt an install and if THAT messes up, throw an error to the user? we could make this even smoother by having a naming convention for an array to run through in
environment.rb and use the SAME array for our rake task. hmmmm...
On 8/13/07, Justin W. Reagor <justinwr@gmail.com
> wrote:Thats definitely true for running the application (or deployment)... but any developer is going to spend the 30 minutes (or more) on a new system anyway, mucking around and finding out how thing operate. And this is where documentation/rdoc helps out extremely.
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]
On 8/13/07, Colin A. Bartlett <phillyonrails@colinabartlett.com
> wrote: Keith Fitzgerald wrote:
> is there a way to tell which gems are required for a given app?
Nothing automatic, to my knowledge.
A number of people have put together scripts or rake tasks that check
for Gems, given a list of those required. Nothing beats just documenting
it, IMHO. We use a Wiki for such things.
--
Colin A. Bartlett
Kinetic Web Solutions
http://blog.kineticweb.com
_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk
_______________________________________________ To unsubscribe or change your settings, visit:
_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk
_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk
|
|