On Sun, Jun 4, 2017 at 4:04 PM Daniel Gruno <[email protected]> wrote:
> On 06/04/2017 09:59 PM, John D. Ament wrote: > > If we use python as the webapp, would you expect to use a python web > > framework (ala django) for the UI? > > No, I would not expect us to use something as heavy as Django - I don't > see the need at present. Our web app is primary a JSON REST API with a > JS overlay, and as such, I think the frames needed are very small. > > I said ala Django. Not only Django, but other frameworks that may be of interest. The reason being - simpler code, lower barrier of entry. I'm curious, how would you consider returning JSON over HTTP with Python? > There is also backwards compat to think about. If we switched to a > python web framework with batteries and kitchen sink, older > installations would need a converter, and likely another database > installed (assuming you meant to imply that django could handle sessions > and such). > > As far as I can tell, Elasticsearch could be that runtime. I don't believe there's any hard requirement to use another database. Where are sessions stored right now? Cookie only? > It is entirely possible that I'm ignorant about what Django would have > to offer here. > > The way I see it, it (it being Django or another framework like Django) becomes a consistent development platform, that handles all of our web handling use cases and is simple enough to run. > With regards, > Daniel. > > > > > On Sun, Jun 4, 2017 at 3:26 PM Daniel Gruno <[email protected]> > wrote: > > > >> Hi folks, > >> I've been pondering about the difficulties PM faces in terms of getting > >> new contributors, and one of the core issues, as I see it, is our choice > >> of using Lua for the web application. Apart from locking people to > >> apache/nginx, it seems that people are - for lack of another word - > >> scared to touch the lua part of it, leaving only 2-3 people working on > it. > >> > >> Therefore, I would like to propose that we switch (after 0.10) to a pure > >> python setup for Pony Mail. Thus, both the archivers and the web app > >> would be python. This would also rid us of a lot of homegrown > >> self-invented wheels within the project. > >> > >> I will of course do my best to help with the bulk of the work here, and > >> I would be immensely grateful if others would support this and help out > >> with the process of converting. I also have acknowledgements from a few > >> people that would like to help with the transition, should we agree on > >> this. > >> > >> So....thoughts? > >> > >> > >> With regards, > >> Daniel. > >> > > > >
