<div dir="ltr">From my perspective - one port for all<div><br></div><div>J</div></div><br><div class="gmail_quote"><div dir="ltr">ne 9. 8. 2015 v 16:39 odesílatel Calin Ciociu <<a href="mailto:calin.ciociu@gmail.com">calin.ciociu@gmail.com</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I can look into changing so all the PyWPS instances run only on 1
flask instance with 1 port only.<br>
Then use like Jonas said .../wps1 and .../wps2 in combination with
that port.<br>
<br>
Is this desired? <br>
Otherwise I will leave it as it is for the moment.<br>
<br>
I changed the default REST url to .../wpsadmin which can be
configured in the PyWPS configuration file under the section
[server].<br>
Just modify the RESTPath attribute value. (has to start with a
leading slash).<br>
<br>
Best regards,<br>
Calin</div><div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<div>On 23.07.15 09:19, Jachym Cepicky
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Jonas: I believe, this is just flask issue, on
apache this should work as expected (flask can handle only singe
request per time)
<div><br>
</div>
<div>flask should not be used in production environment [1]
-> <span style="color:rgb(62,67,73);font-family:Georgia,serif;font-size:17px;line-height:23.7999992370605px">Do
not use the builtin development server in production.</span></div>
<div><span style="color:rgb(62,67,73);font-family:Georgia,serif;font-size:17px;line-height:23.7999992370605px"><br>
</span></div>
<div><span style="color:rgb(62,67,73);font-family:Georgia,serif;font-size:17px;line-height:23.7999992370605px">[1] </span><font color="#3e4349" face="Georgia, serif"><span style="font-size:17px;line-height:23.7999992370605px"><a href="http://flask.pocoo.org/docs/0.10/deploying/" target="_blank"><a href="http://flask.pocoo.org/docs/0.10/deploying/" target="_blank">http://flask.pocoo.org/docs/0.10/deploying/</a></a></span></font></div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">st 22. 7. 2015 v 14:24 odesílatel Jonas Eberle
<<a href="mailto:jonas.eberle@gmx.de" target="_blank">jonas.eberle@gmx.de</a>>
napsal:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">Hi
Calin, </div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">do
you also have in mind to publish several PyWPS instances
on a single port? For operational use I am not keen on
opening a new port for any PyWPS instance in the future.
I would like to use WSGI with Apache Webserver to make
my instances available. Will this still be available
with these developments?</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">I
would like to organize my services as follows (path to
configured in the settings or in the Apache
configuration):</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><a href="http://localhost/wps1" target="_blank"><a href="http://localhost/wps1" target="_blank">http://localhost/wps1</a></a></div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><a href="http://localhost/wps2" target="_blank"><a href="http://localhost/wps2" target="_blank">http://localhost/wps2</a></a></div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">For
the REST administration interface I would then like to
use, e.g. <a href="http://localhost/wpsadmin" target="_blank">http://localhost/wpsadmin</a>
(path to be configured in settings or Apache
configuration). </div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">Best
regards, </div>
</div>
</div>
<div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">Jonas</div>
</div>
</div>
<div>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br>
<span>----- Am 21. Jul 2015 um 17:23 schrieb Calin
Ciociu <<a href="mailto:calin.ciociu@gmail.com" target="_blank">calin.ciociu@gmail.com</a>>:<br>
</span>
<div>
<blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">Hello
everyone,<br>
<br>
I wanted to know people's opinion on the way I am
currently implementing <br>
the REST interface.<br>
Multiple server can be run and managed through the
REST interface <br>
although every server runs with a different port.<br>
So in the end there will be multiple servers running
like for example:<br>
<br>
<a href="http://localhost:5001/wps." target="_blank">http://localhost:5001/wps.</a>..<br>
<a href="http://localhost:5002/wps." target="_blank">http://localhost:5002/wps.</a>..<br>
<a href="http://localhost:5003/wps." target="_blank">http://localhost:5003/wps.</a>..<br>
<br>
On top of these a "sever" is already running which
is handling REST.<br>
It is currently running on port 5000 (which can be
also changed).<br>
<br>
To me this makes sense and seems straightforward.<br>
Is there a better approach?<br>
Should I continue like this?<br>
<br>
<br>
Best regards,<br>
<br>
Calin<br>
_______________________________________________<br>
pywps-dev mailing list<br>
<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</a></blockquote>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
pywps-dev mailing list<br>
<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</a></blockquote>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
pywps-dev mailing list
<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
pywps-dev mailing list<br>
<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev</a></blockquote></div>