How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

legramo
In order to explore and visualize the data from a sensor network i'm trying to deploy the below platform called "52n-helgoland":

https://hub.docker.com/r/geocontainers/52n-helgoland/

As you can see, it's allocated within a Docker container which is already in our servers:
****@wsncentral:~$ sudo docker pull geocontainers/52n-helgoland
Using default tag: latest
latest: Pulling from geocontainers/52n-helgoland
357ea8c3d80b: Pull complete
0fc04568277e: Pull complete
0bed9719ddcb: Pull complete
c8102756fd60: Pull complete
33da8a3f32f0: Pull complete
994df0594cc2: Pull complete
553685634459: Pull complete
abb7e642b7e4: Pull complete
Digest: sha256:81e2869ec4a191a0bfc3714d5f0d8d9e3d40ff908e620ce20d844b28aca07a61
Status: Downloaded newer image for geocontainers/52n-helgoland:latest

root@wsncentral:/etc/docker# docker run -it geocontainers/52n-helgoland
(blank)


Unfortunately i don't know the right steps in order to get the things done... Any advice about which are the right steps would be welcome, thanks in advance!

Regards
Reply | Threaded
Open this post in threaded view
|

Re: How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

debard
Je suis absent du bureau du 04/02/2017 au 13/02/2017 compris.
Je n'ai pas accès à ma messagerie pendant cette période. Je prendrai connaissance de votre message à mon retour.

Cordialement
Reply | Threaded
Open this post in threaded view
|

Re: How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

Daniel Nüst-2
In reply to this post by legramo
Try exposing port 80:

docker run -it -p 80:80 geocontainers/52n-helgoland

Then open http://localhost (or http://host-ip) in the browser.

Hope this helps,
Daniel



On 08/02/17 11:24, legramo wrote:

> In order to explore and visualize the data from a sensor network i'm trying
> to deploy the below platform called "52n-helgoland":
>
> https://hub.docker.com/r/geocontainers/52n-helgoland/
> <https://hub.docker.com/r/geocontainers/52n-helgoland/>  
>
> As you can see, it's allocated within a Docker container which is already in
> our servers:
> /****@wsncentral:~$ sudo docker pull geocontainers/52n-helgoland
> Using default tag: latest
> latest: Pulling from geocontainers/52n-helgoland
> 357ea8c3d80b: Pull complete
> 0fc04568277e: Pull complete
> 0bed9719ddcb: Pull complete
> c8102756fd60: Pull complete
> 33da8a3f32f0: Pull complete
> 994df0594cc2: Pull complete
> 553685634459: Pull complete
> abb7e642b7e4: Pull complete
> Digest:
> sha256:81e2869ec4a191a0bfc3714d5f0d8d9e3d40ff908e620ce20d844b28aca07a61
> Status: Downloaded newer image for geocontainers/52n-helgoland:latest
>
> root@wsncentral:/etc/docker# docker run -it geocontainers/52n-helgoland
> (blank)
> /
>
> Unfortunately i don't know the right steps in order to get the things
> done... Any advice about which are the right steps would be welcome, thanks
> in advance!
>
> Regards
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/How-to-deploy-Helgoland-52-North-Sensor-Web-Client-based-on-JavaScript-tp4028835.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>

--
Daniel Nüst
Institute for Geoinformatics (ifgi),   University of Münster
Heisenbergstraße 2, 48149 Münster, Germany; +49 251 83 31962
http://ifgi.uni-muenster.de/~d_nues01        http://o2r.info
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

legramo
Thanks Daniel, you were right. After executing docker run -it -p 80:80 geocontainers/52n-helgoland the container could be accessed.

Here is the link to it:
http://datavisualization.iecolab.es

Here is the link to the 52º North Server:
http://wsncentral.iecolab.es/observations/

Now comes the most important question... how can i link both? Thanks in advance.

Fran

Reply | Threaded
Open this post in threaded view
|

Re: How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

Daniel Nüst-2


On 08/02/17 14:22, legramo wrote:

> Thanks Daniel, you were right. After executing /docker run -it -p 80:80
> geocontainers/52n-helgoland/ the container could be accessed.
>
> Here is the link to it:
> http://datavisualization.iecolab.es <http://datavisualization.iecolab.es/#/>  
>
> Here is the link to the 52º North Server:
> http://wsncentral.iecolab.es/observations/
> <http://wsncentral.iecolab.es/observations/>  
>
> Now comes the most important question... how can i link both? Thanks in
> advance.

Please check with the helgoland documentation on how to configure your
SOS/Timeseries API.

You can mount your own settings.json file into the container, see
example here:
https://github.com/geocontainers/dockerfiles/tree/master/52n-helgoland

docker run ... -v
/path/to/mysettingsfile_on-the-host-computer.json:/usr/share/nginx/html/settings.json


See https://docs.docker.com/engine/tutorials/dockervolumes/


Hope this helps,
Daniel



>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/How-to-deploy-Helgoland-52-North-Sensor-Web-Client-based-on-JavaScript-tp4028835p4028840.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>

--
Daniel Nüst
Institute for Geoinformatics (ifgi),   University of Münster
Heisenbergstraße 2, 48149 Münster, Germany; +49 251 83 31962
http://ifgi.uni-muenster.de/~d_nues01        http://o2r.info
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

Carsten Hollmann
In reply to this post by legramo
Hi Fran,

the Helgoland client uses the Sensor Web REST-API [0]. In the bundle
package of the 52°North SOS the Sensor Web REST-API is already included.

I have checked your SOS instance by calling the Sensor Web REST-API but
it looks like you have installed the normal 52N SOS package (only SOS).

This is the URL to check if the REST-API is supported:

http://wsncentral.iecolab.es/observations/api/v1/

The 52N SOS bundle package can be downloaded from here:

 
https://github.com/52North/SOS/releases/download/v4.3.9/52n-sensorweb-sos-bundle-4.3.9.zip

Best,
Carsten

[0] https://52north.github.io/series-rest-api/
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: How to deploy "Helgoland" 52°North Sensor Web Client based on JavaScript

legramo
Hi Carsten,

Thanks for your advice, you were absolutely right! After deploying https://github.com/52North/SOS/releases/download/v4.3.9/52n-sensorweb-sos-bundle-4.3.9.zip Helgoland is running perfectly. No docker needed.

Regards,
Fran