<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Hello, <br /> <br />this is, what I meant: I've got forked PyWPS installed in Virtualenv in the develop mode, where resides my gsoc-pywps-app (<a href="https://github.com/jan-rudolf/gsoc-pywps-app" target="_blank" rel="noreferrer">https://github.com/jan-rudolf/gsoc-pywps-app</a>), which is served by Apache. I've edited my forked PyWPS and added Flask application, that is going to serve URL's (<a href="https://github.com/jan-rudolf/pywps/tree/master/pywps/server" target="_blank" rel="noreferrer">https://github.com/jan-rudolf/pywps/tree/master/pywps/server</a>) - it's serving random (not relevant) URLs now from my example of using Flask with Apache. So it's part of PyWPS, the user will easily plug the application by import statement and connect with his web server (Apache/Nginx) like <a href="https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py" target="_blank" rel="noreferrer">https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py</a> - lines 12 and 23. It has not pretty names and line 23 is going to look like assigning constructor with a config file as a parameter (or similar) - it's about the principle, it will look better.<br /> <br />We are going to have a discussion with Jachym about REST API, so that will form the content of the Flask application. I would like also write some kind of documentation, so anyone could try it run.<br /> <br />Jan<br /> <br /> <br />On 2016-06-07 12:02, Jan Rudolf wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Send it again (mistakes in English): Yes, I didn't mean using Flask as a<br /> production web server, I count<br /> on Apache/Nginx, but a Flask app for URL handling and web related stuff.<br /> <br /> On 2016-06-07 11:57, Jan Rudolf wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Yes, I didn't mean not using Flask as a production a webserver, I count<br /> on Apache/Nginx, but a Flask app for URL handling and web related stuff.<br /> <br /> On 2016-06-07 09:21, Jachym Cepicky wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Just noting: AFAIK we had already problem with Calin some time back,<br /> flask server was not able to handle more requests at once, Calin tried<br /> to run the administrative interface on different port, but I<br /> personally dislike such solution.<br /> <br /> IMHO the production environment is Apache2/Nginx - we shall focus on<br /> that<br /> <br /> J<br /> <br /> po 6. 6. 2016 v 23:06 odesílatel Jan Rudolf <<a href="mailto:rudolja1@fit.cvut.cz">rudolja1@fit.cvut.cz</a>><br /> napsal:<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Hello,<br /> <br /> Settings: yes, I plan to do it.<br /> <br /> I have been reading a source code of PyWPS and demo applications in<br /> order to get a clear picture. I have a meeting with Jachym about<br /> REST<br /> API on Wednesday, so I would like to implement now an integration of<br /> Flask app into PyWPS with URL handling. I understand that Service.py<br /> acts as a WSGI application, it's the core thing. I have it as an<br /> entry<br /> point here<br /> <a href="https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py" target="_blank" rel="noreferrer">https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py</a>.<br /> Because we want the web-based administration with own URLs, so I<br /> would<br /> like to make as the entry point Flask's WSGI connection with defined<br /> URL's based on your wishes and one of the URL for Service.py purpose<br /> -<br /> similarly as in one of the demo application. So this functionality,<br /> I<br /> would like to integrate for example into /pywps/webserver/, where<br /> would<br /> be class Server/Webserver with this features and all the related web<br /> (Flask) files. So user would, instead of pointing to<br /> Service.py/Service<br /> (<a href="https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py" target="_blank" rel="noreferrer">https://github.com/jan-rudolf/gsoc-pywps-app/blob/master/wsgi.py</a>),<br /> assign Server(config=config_file).run() (or similar) and it will run<br /> classic PyWPS with our extended URLs. Make it copy-paste-run for the<br /> user. What do you think? OR I will just implement it with my forked<br /> version and we can discuss it better.<br /> <br /> After this, process control will come in.<br /> <br /> Jan Rudolf<br /> <br /> On 2016-06-06 20:46, Jachym Cepicky wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Hi Jan,<br /> <br /> nice work<br /> <br /> would it be possible to document your settings and so on in PyWPS<br /> documentation? Take is as part of your work ;-)<br /> <br /> J<br /> <br /> ne 5. 6. 2016 v 21:18 odesílatel Jan Rudolf</blockquote>
<<a href="mailto:rudolja1@fit.cvut.cz">rudolja1@fit.cvut.cz</a>>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">napsal:<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Hello,<br /> <br /> here is my week report<br /> <a href="http://gsoc-2016.jan-rudolf.cz/article/second-week-report" target="_blank" rel="noreferrer">http://gsoc-2016.jan-rudolf.cz/article/second-week-report</a>.<br /> <br /> Best regards, Jan Rudolf<br /> _______________________________________________<br /> SoC mailing list<br /> <a href="mailto:SoC@lists.osgeo.org">SoC@lists.osgeo.org</a><br /> <a href="http://lists.osgeo.org/mailman/listinfo/soc" target="_blank" rel="noreferrer">http://lists.osgeo.org/mailman/listinfo/soc</a></blockquote>
</blockquote>
_______________________________________________<br /> pywps-dev mailing list<br /> <a href="mailto:pywps-dev@lists.osgeo.org">pywps-dev@lists.osgeo.org</a><br /> <a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank" rel="noreferrer">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a></blockquote>
</blockquote>
_______________________________________________<br /> pywps-dev mailing list<br /> <a href="mailto:pywps-dev@lists.osgeo.org">pywps-dev@lists.osgeo.org</a><br /> <a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank" rel="noreferrer">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a></blockquote>
_______________________________________________<br /> pywps-dev mailing list<br /> <a href="mailto:pywps-dev@lists.osgeo.org">pywps-dev@lists.osgeo.org</a><br /> <a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank" rel="noreferrer">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a></blockquote>
</div>
</body></html>