Added optional config setup

[notch8]

First off, thanks for maintaining a great template. I've been really happy with it, though there are a few things I was starting to change every time. For a while I've been maintaining me own branch with capistrano instead of inploy, exceptional instead of hoptoad and no inherited resource. It occured to me at RubyConf that it would be a lot better to merge with options and push upstream instead of just maintaining my branch forever. This pull request accomplishes that. It allows for the creation of an optional ~/.rails3_template.yml file where different gems can be turned off. I defaulted the config to use your current setup as the default (so exceptional and capistrano default to off).

What do you think?

Best,
Rob Kaufman

[dcrec1]

Hi Rob, I think it's a great idea! Just a few questions, can't be have options like 'rspec' instead of 'no_rspec'? I think its more clear, what do you think?

About the Capistrano and Exceptional options, maybe we can declare extra dependencies in the same yml file and read them in the template, what do you think?

[notch8]

I went with "no_" under the thought that it was more likely you'd want to include something (and thus not have to add a config entry for it). Switching it around is easy, but that would necessitate a larger quantity of config options for default operation. Let me know if you still think it would be better switched

The yml file goes in the users home directory (not in the repo). I guess we could create the default file with those keys in the event there is no ~/.rails3_template.yml file. Is that what you are suggesting?

[dcrec1]

About the second point, im suggesting maybe we can have something like this in the yml file:

extra:
gem:
capistrano: '>=1.2.3'
exceptional: '=0.5'
plugin:
lorem: 'git://...'

And then read this things in the template, so if somebody wants the template plus an specific gem, he has only to define it in the yml file. Thinking better about this, maybe we can read from and rb file and require it in the template, so people can specify all the new dependencies using the rails syntax:

gem 'name, 'version'
...

Hope this time it got clearer :P

[notch8]

nope dude, that's less clear not more clear, sorry :p

The template itself needs to support version of whatever is being included at whatever versions, otherwise it stops really being useful at all. Having to update the yml file for each version means keeping the version info in two places, which I don't think makes sense.

I'm not 100% sure you're understanding the way the yml file vs the defaults currently works. Right now if you have a yml file in your home directory it reads that and turns off whatever you specify there. Because I didn't want to force you or other existing users to create the yml file before using the template I set capistrano and exceptional as off (since you should not have both exceptional and hoptoad at the same time and should not have both capistrano and inploy at the same time). That way if you use this update it changes nothing for you or existing users until they decide to create a yml file and turn something off.