[Pywps-dev] [SoC] [SOC] Week report - Web-based administration and process control for PyWPS

Jan Rudolf rudolja1 at fit.cvut.cz
Tue Jun 7 03:02:22 PDT 2016


Send it again (mistakes in English): Yes, I didn't mean using Flask as a
production web server, I count
on Apache/Nginx, but a Flask app for URL handling and web related stuff.

On 2016-06-07 11:57, Jan Rudolf wrote:
> Yes, I didn't mean not using Flask as a production a webserver, I count
> on Apache/Nginx, but a Flask app for URL handling and web related stuff.
> 
> On 2016-06-07 09:21, Jachym Cepicky wrote:
>> Just noting: AFAIK we had already problem with Calin some time back,
>> flask server was not able to handle more requests at once, Calin tried
>> to run the administrative interface on different port, but I
>> personally dislike such solution.
>>
>> IMHO the production environment is Apache2/Nginx - we shall focus on
>> that
>>
>> J
>>
>> po 6. 6. 2016 v 23:06 odesílatel Jan Rudolf <rudolja1 at fit.cvut.cz>
>> napsal:
>>
>>> Hello,
>>>
>>> Settings: yes, I plan to do it.
>>>
>>> I have been reading a source code of PyWPS and demo applications in
>>> order to get a clear picture. I have a meeting with Jachym about
>>> REST
>>> API on Wednesday, so I would like to implement now an integration of
>>> Flask app into PyWPS with URL handling. I understand that Service.py
>>> acts as a WSGI application, it's the core thing. I have it as an
>>> entry
>>> point here
>>> https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py.
>>> Because we want the web-based administration with own URLs,  so I
>>> would
>>> like to make as the entry point Flask's WSGI connection with defined
>>> URL's based on your wishes and one of the URL for Service.py purpose
>>> -
>>> similarly as in one of the demo application. So this functionality,
>>> I
>>> would like to integrate for example into /pywps/webserver/, where
>>> would
>>> be class Server/Webserver with this features and all the related web
>>> (Flask) files. So user would, instead of pointing to
>>> Service.py/Service
>>> (https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py),
>>> assign Server(config=config_file).run() (or similar) and it will run
>>> classic PyWPS with our extended URLs. Make it copy-paste-run for the
>>> user. What do you think? OR I will just implement it with my forked
>>> version and we can discuss it better.
>>>
>>> After this, process control will come in.
>>>
>>> Jan Rudolf
>>>
>>> On 2016-06-06 20:46, Jachym Cepicky wrote:
>>>> Hi Jan,
>>>>
>>>> nice work
>>>>
>>>> would it be possible to document your settings and so on in PyWPS
>>>> documentation? Take is as part of your work ;-)
>>>>
>>>> J
>>>>
>>>> ne 5. 6. 2016 v 21:18 odesílatel Jan Rudolf
>>> <rudolja1 at fit.cvut.cz>
>>>> napsal:
>>>>
>>>>> Hello,
>>>>>
>>>>> here is my week report
>>>>> http://gsoc-2016.jan-rudolf.cz/article/second-week-report.
>>>>>
>>>>> Best regards, Jan Rudolf
>>>>> _______________________________________________
>>>>> SoC mailing list
>>>>> SoC at lists.osgeo.org
>>>>> http://lists.osgeo.org/mailman/listinfo/soc
>>> _______________________________________________
>>> pywps-dev mailing list
>>> pywps-dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/pywps-dev
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pywps-dev


More information about the pywps-dev mailing list