This allows abstracting configs such as tokens from the yaml file in setups like Heroku, that are readonly. By using ERB it's possible to make use of ENV vars to configure the yaml file.
I've also made some minor refactorings, removed a deprecation warning from RSpec, and changed the gemfile to use ~> for ActiveResource and RSpec dependencies. All tests are green.
Let me know if something can be improved, thanks.
Prefer ~> over >= for gems in gemspec
There is a great chance for this to break with versions like Rails 4
(that has just removed ActiveResource from core) or RSpec 3 when
released. Use a safer setup.
Only use attr_writer for primary_key, as the reader method exists
Remove rspec deprecation warning and add default task
So you can run "rake" instead of "rake spec"
Refactor rails spec
Allow configure using yaml ERB files
This allows using ENV vars and other ERB goodness if required. A good
example is to use with heroku ENV vars.
oh man thanks for doing this! I've wanted to do it for some time.
@mahmoudimus thanks :)