<div dir="ltr">Hi Daniel,<div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I want to use paraview web with SSL. As far as I understand I need apache as a proxy server for that? Or is it possible with pvpython?<br></blockquote><div><br></div><div>It might be possible with pvpython, but I've never done it, I've always used apache to rely on a single opened port and handle the encryption. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I have my own launcher which opens pvpython with a different port for each user. Is this the right way? Will this work with ssl?<br></blockquote><div><br></div><div>If pvpython directly support the wss connection, you can be good. Usually the setup, that I do is that I have Apache serving only the port 443 (https) for both the static content and the (wss) websocket endpoint. And I use a mapping file between the Websocket endpoint that get returned by my launcher and the host/port I should connect to on the backend to establish the link between the client and the actual ParaViewWeb server instance.</div><div><br></div><div>But that does not mean, that's the only way to do it and if you don't mind having several port open, I don't see why it could not work.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Concerning:<br>
<br>
<a href="https://kitware.github.io/visualizer/docs/" rel="noreferrer" target="_blank">https://kitware.github.io/visu<wbr>alizer/docs/</a><br>
<br>
The web visuailzer should work via npm installation? It does not work for me:<br>
C:\Users\danie\AppData\Roaming<wbr>\npm\node_modules\pvw-visualiz<wbr>er\bin\pvw-visualizer-cli.js:<wbr>41<br>
var pvPythonExecs = find(paraview).filter(function<wbr>(file) { return file.match(/pvpython$/) || file.match(/pvpython.exe$/); });<br>
^<br>
<br>
TypeError: find(...).filter is not a function<br>
at Object.<anonymous> (C:\Users\danie\AppData\Roamin<wbr>g\npm\node_modules\pvw-visuali<wbr>zer\bin\pvw-visualizer-cli.js:<wbr>41:36)<br>
at Module._compile (module.js:409:26)<br>
at Object.Module._extensions..js (module.js:416:10)<br>
at Module.load (module.js:343:32)<br>
at Function.Module._load (module.js:300:12)<br>
at Function.Module.runMain (module.js:441:10)<br>
at startup (node.js:139:18)<br>
at node.js:968:3<br></blockquote><div><br></div><div>Well, I guess I haven't tried to run the new Visualizer server on a Windows machine. </div><div>But with ParaView 5.2 (yet to be released), we should have a ParaViewWeb back in the binaries. So we should make sure our Visualizer command line tool work on that platform as well.</div><div>Although, the command line is more for beginners than anything else as it only simplify the demo usage. In real word deployment, with a launcher, the true pvpython command line should be used instead.</div><div><br></div><div>Here is an example of what you should see in a working environment:</div><div><br></div><div>
<div>$ Visualizer -d ~/Downloads/</div><div><br></div><div>===============================================================================</div><div>| Execute:</div><div>| $ /Applications/paraview.app/Contents/bin/pvpython</div><div>| -dr</div><div>| /Users/seb/Documents/code/Web2/visualizer/server/pvw-visualizer.py</div><div>| --content</div><div>| /Users/seb/Documents/code/Web2/visualizer/dist</div><div>| --port</div><div>| 8080</div><div>| --data</div><div>| /Users/seb/Downloads/</div><div>===============================================================================</div><div><br></div><div>[...]</div><div><br></div>
-- <br>
Daniel Zuidinga<br>
Dipl.-Ing.<br>
<br>
SEO Aachen<br>
Passstr. 5<br>
52070 Aachen<br>
<br>
Tel : 0241 / 450 912 67<br>
E-Mail: <a href="mailto:info@seoaachen.de" target="_blank">info@seoaachen.de</a><br>
Web : <a href="http://www.seoaachen.de" rel="noreferrer" target="_blank">http://www.seoaachen.de</a> (nur zum Teil aktuell)<br>
Xing : <a href="https://www.xing.com/profile/Daniel_Zuidinga" rel="noreferrer" target="_blank">https://www.xing.com/profile/D<wbr>aniel_Zuidinga</a><br>
<br>
Bald online: Software Tools für Konstrukteure und Bauteilhersteller<br>
<a href="http://www.engineeringonline.de" rel="noreferrer" target="_blank">http://www.engineeringonline.d<wbr>e</a><br>
<br>
______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaV<wbr>iew</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview</a><br>
</div></div><br></div></div>