Ask HN: Best approach for adding an API to an existing rails app
4 comments
Make sure you give RocketPants a look:
https://github.com/filtersquad/rocket_pants
https://github.com/filtersquad/rocket_pants
Check out Grape. (https://github.com/intridea/grape/)
Here are a couple of tutorials which may get your brain juices flowing...
http://railscasts.com/episodes/322-rabl?view=asciicast
http://railscasts.com/episodes/352-securing-an-api?view=asci...
http://railscasts.com/episodes/348-the-rails-api-gem?view=as...
http://railscasts.com/episodes/322-rabl?view=asciicast
http://railscasts.com/episodes/352-securing-an-api?view=asci...
http://railscasts.com/episodes/348-the-rails-api-gem?view=as...
Cool. Thanks man.
VVX.IO was my first full end-to-end just-me programming experiment. I was up until this a front-end and product guy (don't even code in my day job - the game is a part time labour of love) - so approaches to an API are new to me - there seem to be a lot of options and guidelines out there for offering APIs - from 3rd party services (mashape) to best-practice on auth etc. - what would you guys recommend as a good place to start?
Thanks a lot!