Thank you very much for your commit to add a link to the app and also for your informative reply Stephen, really appreciate it! The other API project that you mentioned in you links above seems to have just one main contributor and doesn't look to have been particularly active in the last half year or so from the quick glimpse I had (unless I was looking at the wrong repo). It'll be interesting to see how it turns out and how the API specification for that project evolves.
For those of you interested in the REST API I have been working on, the latest major update (0.3.0) is now available on PyPi and Github. It also now has documentation available at http://gcushen.github.io/mezzanine-api to help you get started using the API :) If anyone has feedback or API features they would like to see in mezzanine-api, just let me know and I can try to prioritize those features! I am currently working on some interesting aspects of the API roadmap (listed at the aforementioned documentation website), including a test suite. George On Wednesday, 13 May 2015 21:55:36 UTC+1, Stephen McDonald wrote: > > Hey no harm in all in having a separate project, so don't worry! I even > added it to the list of third party apps just now: > > > https://github.com/stephenmcd/mezzanine/commit/b4ef263f163d38465ce2d8591a753910859eb1de > > I found a couple of threads where we talked about it. Here's the first > mention from a couple years ago: > > > https://groups.google.com/forum/#!searchin/mezzanine-users/drf/mezzanine-users/EpHIx7fTkmY/Suo2X2z2e7gJ > > Not much info there, but then later last year we started a real discussion > here: > > > https://groups.google.com/forum/#!searchin/mezzanine-users/drf/mezzanine-users/BW0Xjn5Zwvg/kqoonBOP3ikJ > > I wrote a longer reply around the middle of that thread with a rough idea > on what we might do with DRF inside Mezzanine itself. > > > > On Thu, May 14, 2015 at 6:48 AM, Geo <[email protected] <javascript:>> > wrote: > >> That's interesting. I'm very surprised to hear that. When I was >> researching, I found a huge number of requests for an API but no proper >> implementations whatsoever. About the closest thing I found was a post by >> Stephen on Github Issues from about 8 months ago stating something along >> the lines of a REST API would definitely not be included in Mezzanine >> itself and anyone who attempts it should design it as a third party app. I >> did not find any such third party apps. I guess your vision suddenly >> changed sometime since then. Anyway, I can still see a number of benefits >> to the one I'm developing, especially in relation to Oauth2 authentication, >> working on writable access features, documentation and testing. As well as >> being available now as an easy to use add-on. >> >> I might be interested to discuss combining our efforts on this. Although >> the projects have some differences and might have different roadmaps and >> goals - I could not find in that Github Convo you referenced what those are >> exactly for you and what your intentions are with regards to an API? >> >> Cheers, >> George >> >> On Wednesday, 13 May 2015 20:41:54 UTC+1, Stephen McDonald wrote: >>> >>> Wow! >>> >>> This looks really cool. There's a similar piece of work going on here >>> with the intention of residing in Mezzanine itself: >>> >>> https://github.com/stephenmcd/mezzanine/pull/1210 >>> >>> Not sure if there's anything the two bits of work can leverage off each >>> other, or how that might turn out, but what you've done looks great. >>> >>> On Thu, May 14, 2015 at 5:14 AM, Geo <[email protected]> wrote: >>> >>>> Hi all, >>>> >>>> I have recently been working on a RESTful web API for Mezzanine which >>>> can help empower developers to automate, extend and combine Mezzanine with >>>> other services. This may be particularly useful to you if you are >>>> interested in working on an innovative front end for your blog/CMS using a >>>> modern framework such as Ember.js. >>>> >>>> The project is currently in its early stages. Version 0.2 has just been >>>> released which features: >>>> >>>> * REST API resources for posts, pages, users, and categories >>>> * Apply filters and search queries to narrow down results >>>> * OAuth 2.0 allows users to authorize and revoke access to third >>>> party applications without the need for those applications to request the >>>> user's credentials >>>> * Web browsable API >>>> * Endpoints documented with Swagger UI >>>> * Leverages Django Rest Framework >>>> >>>> There is also a roadmap for the future which at the time of writing >>>> includes: >>>> >>>> * More endpoints >>>> * Writeable API access >>>> * Test Suite >>>> * Further documentation >>>> >>>> You can install it with: >>>> >>>> pip install mezzanine-api >>>> >>>> And then go to PyPi or Github to follow the rest of the setup procedure: >>>> >>>> PyPi: https://pypi.python.org/pypi/mezzanine-api >>>> Github: https://github.com/gcushen/mezzanine-api >>>> >>>> Let me know if you have any feedback and feel free to discuss the API >>>> here :) >>>> >>>> Cheers, >>>> >>>> George >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Mezzanine Users" 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/d/optout. >>>> >>> >>> >>> >>> -- >>> Stephen McDonald >>> http://jupo.org >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Stephen McDonald > http://jupo.org > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" 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/d/optout.
