[LRUG] CMS for bespoke API

[Nick Novitski]

There's also https://github.com/rails-api/active_model_serializers

- Nick Novitski <http://nicknovitski.com> (stuff i've
done<https://github.com/nicknovitski/>
)


On Tue, Sep 10, 2013 at 12:16 PM, Oto Brglez <otobrglez at gmail.com> wrote:

> Hey!
>
> RABL is quite outdate -at least from what is going on on their GH.
> I suggest that you look into DHH's jbuilder
> https://github.com/rails/jbuilder
>
> - Oto
>
>
>
> On Sep 10, 2013, at 8:40 PM, Agustin Viñao <agustinvinao at gmail.com> wrote:
>
> A nice gem to work with json views is https://github.com/nesquena/rabl,
> you can create json, xml or many other templates formats.
>
> Is a good way to build an api from a Rails app.
>
> --
> --
> Agustin Viñao
>
> *Paradox*: Life is a mystery. Don't waste time trying to figure it out. /
> *Humor*: Keep a sense of humor, especially about yourself. It is a
> strength beyond all measure. / *Change*: Know that nothing stays the same.
> Web Developer - Ruby - Ruby On Rails - T.D.D.
>
> m: agustinvinao at gmail.com
> t: http://twitter.com/agustinvinao
> w: http://www.agustinvinao.com.ar
> g: http://github.com/agustinvinao
> l: http://ar.linkedin.com/in/agustinvinao
> f: http://www.facebook.com/saltoaciegas
> g+: http://profiles.google.com/agustinvinao
>
>
> On Tue, Sep 10, 2013 at 2:32 PM, George Ornbo <george at shapeshed.com>wrote:
>
>> Depending on the complexity of the client I'd favour something like
>> Backbone to create the client. If you are talking to a RESTful API it is
>> pretty straightforward to create a CRUD app presuming your API handles auth
>> and roles somehow.
>>  On 10 Sep 2013 17:47, "Oto Brglez" <otobrglez at gmail.com> wrote:
>>
>>> Hey Ian!
>>>
>>> I would suggest that you look into this two project...
>>> - https://parse.com/
>>> - http://helios.io/
>>>
>>> - Oto
>>>
>>>
>>> On Sep 10, 2013, at 6:30 PM, Ian Kynnersley <iankynnersley at gmail.com>
>>> wrote:
>>>
>>> Hi all,
>>>
>>> For an upcoming project, I will be creating an API to power some mobile
>>> apps. The API will be largely read-only in JSON and will need to provide an
>>> admin interface for non-technical users to manage the data that drives it.
>>>
>>> By default, I would probably knock up something bespoke with Rails and
>>> RailsAdmin. Or maybe a Sinatra equivalent. However, there would be definite
>>> benefits on this project to building it on an established CMS platform
>>> rather than completely hand-coded.
>>>
>>> Has anyone got any experience of using an existing CMS to create an API
>>> like this without a "public" web interface.
>>>
>>> Is there anything specific I need to consider when using existing CMS
>>> tools or is it as simple as finding one that allows API-suitable
>>> authentication (i.e. not forms-based) and then creating JSON templates
>>> rather than HTML ones?
>>>
>>> Thanks for your help!
>>>
>>> Ian
>>>
>>> --
>>>
>>> Ian Kynnersley
>>> http://iankynnersley.co.uk | +44 (0) 7973 420 829 |
>>> http://twitter.com/kpopper
>>> _______________________________________________
>>> Chat mailing list
>>> Chat at lists.lrug.org
>>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>>>
>>>
>>>
>>> _______________________________________________
>>> Chat mailing list
>>> Chat at lists.lrug.org
>>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>>>
>>>
>> _______________________________________________
>> Chat mailing list
>> Chat at lists.lrug.org
>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>>
>>
>
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130910/59e130f5/attachment-0003.html>