Patrick Mulder

Additionally, some interesting variation might be include Redis or some store to load data from a DB, instead of files.

Thanks, indeed, placing the JSON in the public works too. The approach with Sinatra then only would make sense, when a resources/files would be created, or a database would be...

Well, some of the original idea was to have some way to get started with API development in Ruby too. A similar approach to: http://www.arangodb.org/foxx and more ideas on API...

I find running the tests not so easy, i.e. I was exploring how to make this project run with an SQL orm adapter (see https://github.com/mulderp/rack-oauth2-server/tree/active_record ) However, as far as...

Another issue is upgrading Shoulda, since it includes a broken version of Mocha, if I see correctly :https://github.com/freerange/mocha Versions 0.10.2, 0.10.3 & 0.11.0 of the Mocha gem were broken

Hmm.. I think the problem is shoulda-matchers, requiring bourne: ``` shoulda-matchers (1.4.2) activesupport (>= 3.0.0) bourne (~> 1.1.2) ``` And bourne requires an old Mocha version. But indeed it's possible...

The names of the Gems might become: - oauth2-sinatra - oauth2-active_record - oauth2-active_model etc.

Thanks Brian! The article on the repository pattern looks very helpful indeed. About the extraction issue, my feeling was that some boilerplate could be removed when working in separate projects...

I discovered: https://github.com/trumant/rack-oauth2-server-active-record/commits/active_record That looks like having a separate sub-repo for AR interesting, but I need to experiment to understand better.

Hm.. this looks like an interesting plugin for Rack too to handle storage of tokens: https://github.com/minad/moneta