Hey Jon,

For Rails APIs, you should also take a second look at Grape.  I may be a 
bit biased because I work at Intridea, but Grape has come a long way in the 
last year and has built some pretty good momentum.

peter


On Saturday, March 16, 2013 3:30:06 PM UTC-7, mr.jonc wrote:
>
> I'm looking for some advice. I'm building an iOS application that does the 
> typical things that iOS applications do: talk to a rest api to get things 
> like user generated photos and info, and allow users to register and login 
> and submit photos and other information. Imagine essentially the same api 
> that instagram would have.
>
> I know (knew) rails well but it's been about a year since I did my last 
> rails app. I was actually considering doing this in Node, but there are 
> some limitations node has around server side intensive processing that I 
> knew we would hit eventually.
>
> So, I'm back to Rails. My question is, where do I go to figure out how 
> people are starting new rails apps these days? What versions of ruby/rails 
> should I use? It used to be you just did 'rails <name of your project>' and 
> then built scaffolds and deleted a bunch of files. But I don't need a web 
> app, and there's probably some Rest API bootstrapper or something out 
> there...
>
> What do you think? Anything I should take a look at?
> Thanks,
> --Jon
>

-- 
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--- 
You received this message because you are subscribed to the Google Groups "SD 
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to