<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Julierme,<div class=""><br class=""></div><div class="">I think you had docker-compose stop (and docker-compose start) in mind?</div><div class="">docker-compose down will remove your containers + networks.</div><div class="">(-v for volumes as well … see —help for more).</div><div class=""><br class=""></div><div class="">cheers,</div><div class=""><br class=""></div><div class="">Toni</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="">-----------------------------------------------</div><div class="">CSGIS</div><div class=""><br class=""></div><div class="">-----------------------------------------------</div><div class=""><div class="" style="orphans: 2; widows: 2;">Kolonnadenstraße 1</div><div class="" style="orphans: 2; widows: 2;">04109 Leipzig</div></div><div class="">-----------------------------------------------</div><div class="">Mobil<span class="Apple-tab-span" style="white-space: pre;"> </span>+49/ (0) 176 6680 3198</div><div class="">Tel <span class="Apple-tab-span" style="white-space: pre;"> </span>+49/ (0) 341 24 04 738</div><div class="">Fax <span class="Apple-tab-span" style="white-space: pre;"> </span>+49/ (0) 341 24 04 73</div><div class="">Web<span class="Apple-tab-span" style="white-space: pre;"> </span><a href="http://csgis.de" class="">http://csgis.de</a></div><div class="">-----------------------------------------------</div><div class=""><br class=""></div><div class="">Hinweis gemäß § 33 BDSG</div><div class="">Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument ist ausschließlich für den </div><div class="">Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls Sie diese E-Mail versehentlich </div><div class="">erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und löschen Sie diese Nachricht </div><div class="">von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung, Vervielfältigung, Veränderung, </div><div class="">Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.</div></div></div></div></div></div></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Am 17.09.2018 um 21:00 schrieb <a href="mailto:geonode-users-request@lists.osgeo.org" class="">geonode-users-request@lists.osgeo.org</a>:</div><br class="Apple-interchange-newline"><div class=""><div class="">Send geonode-users mailing list submissions to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:geonode-users@lists.osgeo.org" class="">geonode-users@lists.osgeo.org</a><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>https://lists.osgeo.org/mailman/listinfo/geonode-users<br class="">or, via email, send a message with subject or body 'help' to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>geonode-users-request@lists.osgeo.org<br class=""><br class="">You can reach the person managing the list at<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>geonode-users-owner@lists.osgeo.org<br class=""><br class="">When replying, please edit your Subject line so it is more specific<br class="">than "Re: Contents of geonode-users digest..."<br class=""><br class=""><br class="">Today's Topics:<br class=""><br class=""> 1. Re: GeoNode Project master Docker - Upload layers<br class=""> (Julierme Pinheiro)<br class=""> 2. Re: GeoNode Project master Docker - Upload layers<br class=""> (Julierme Pinheiro)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Mon, 17 Sep 2018 14:36:07 -0300<br class="">From: Julierme Pinheiro <juliermeopensourcedeveloper@gmail.com><br class="">To: francesco bartoli <xbartolone@gmail.com><br class="">Cc: Simone Dalmasso <simone.dalmasso@gmail.com>, geonode-users<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><geonode-users@lists.osgeo.org><br class="">Subject: Re: [GeoNode-users] GeoNode Project master Docker - Upload<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>layers<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><CAKTKyJJtCV7GeVp1kXgc33YPODE9OpFj1_LDStcHUGHR2fYezw@mail.gmail.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">Hi Francesco,<br class=""><br class="">Thank you very much for your reply. I have GeoNode-Project@2.7 installed<br class="">via Docker in a Centos7 VM and I had edited the templates html (site_base<br class="">and site_index) and css file (site_base). GeoNode site was working<br class="">smoothly. But lately, after running docker-compose down and right after<br class="">docker-compose up, this last command resets the django container (the<br class="">container gets a new ID), and why I see that, after running docker-compose<br class="">up the templates [1] and static [2] returns to their default configuration.<br class="">[1]<br class="">https://github.com/GeoNode/geonode-project/tree/2.7/project_name/templates<br class="">[2]<br class="">https://github.com/GeoNode/geonode-project/tree/2.7/project_name/static/css<br class=""><br class="">I appreciated your time<br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class=""><br class="">On Mon, Sep 17, 2018 at 2:02 PM francesco bartoli <xbartolone@gmail.com><br class="">wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi Julierme,<br class=""><br class="">the master branch is not supposed to be always in a safe docker build, at<br class="">least until we could have time and maybe sponsors to introduce a reliable<br class="">CI/CD procedure.<br class=""><br class="">With regards to the sentence "Django container gets a new one every time<br class="">docker-compose up is run.", can you please elaborate more the issue? Is not<br class="">clear what you are facing with.<br class=""><br class="">Thanks,<br class="">Francesco<br class=""><br class="">Il giorno lun 17 set 2018 alle ore 18:52 Julierme Pinheiro <<br class="">juliermeopensourcedeveloper@gmail.com> ha scritto:<br class=""><br class=""><blockquote type="cite" class="">Hi Simone,<br class=""><br class="">I have several instances of GeoNode-Project in different VMs.<br class=""><br class="">GeoNode-Project@2.7 Docker Centos7 VM<br class="">Issue:<br class="">Django container gets a new one every time docker-compose up is run.<br class=""><br class="">GeoNode-Project@2master Docker Centos7 VM<br class="">Issue:<br class="">Related to upload layers<br class="">*Unable to<br class="">usecom.vividsolutions.jts.geom.impl.CoordinateArraySequenceFactory@32f58c5e<br class="">to produce CoordinateSequence with dimension 2*<br class=""><br class="">Thank you very much for your reply. I appreciated your time.<br class=""><br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">On Sat, Sep 15, 2018 at 5:18 AM Simone Dalmasso <<br class="">simone.dalmasso@gmail.com> wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">which version of GeoNode are you using. Keep in mind that the<br class="">geonode-project branch you use should follow the geonode's version.<br class=""><br class="">Best<br class=""><br class="">Il giorno ven 14 set 2018 alle ore 22:37 Julierme Pinheiro <<br class="">juliermeopensourcedeveloper@gmail.com> ha scritto:<br class=""><br class=""><blockquote type="cite" class="">Dear users,<br class=""><br class="">I had geonode-project@2.7 running perfectly fine, including uploading<br class="">layers. Now, I am running GeoNode-Project@master, but I am unable to<br class="">upload data layers. The following message is shown at the end of the<br class="">uploading layers process:<br class="">*Unable to<br class="">usecom.vividsolutions.jts.geom.impl.CoordinateArraySequenceFactory@32f58c5e<br class="">to produce CoordinateSequence with dimension 2*<br class=""><br class="">This would not happen on version 2.7<br class=""><br class="">Any comment on this issue would be very appreciated.<br class=""><br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class=""><br class="">_______________________________________________<br class="">geonode-users mailing list<br class="">geonode-users@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/geonode-users<br class=""><br class=""></blockquote><br class=""><br class="">--<br class="">Simone<br class=""><br class=""></blockquote>_______________________________________________<br class="">geonode-users mailing list<br class="">geonode-users@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/geonode-users<br class=""><br class=""></blockquote><br class=""></blockquote>-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20180917/6e229744/attachment-0001.html><br class=""><br class="">------------------------------<br class=""><br class="">Message: 2<br class="">Date: Mon, 17 Sep 2018 14:37:42 -0300<br class="">From: Julierme Pinheiro <juliermeopensourcedeveloper@gmail.com><br class="">To: francesco bartoli <xbartolone@gmail.com><br class="">Cc: Simone Dalmasso <simone.dalmasso@gmail.com>, geonode-users<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><geonode-users@lists.osgeo.org><br class="">Subject: Re: [GeoNode-users] GeoNode Project master Docker - Upload<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>layers<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><CAKTKyJ+hyezqUtBbvwf5HCN5u2_RF43DbcOUKm2g0rmptMMThg@mail.gmail.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">... their default configuration [1] and [2]<br class=""><br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class="">On Mon, Sep 17, 2018 at 2:36 PM Julierme Pinheiro <<br class="">juliermeopensourcedeveloper@gmail.com> wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi Francesco,<br class=""><br class="">Thank you very much for your reply. I have GeoNode-Project@2.7 installed<br class="">via Docker in a Centos7 VM and I had edited the templates html (site_base<br class="">and site_index) and css file (site_base). GeoNode site was working<br class="">smoothly. But lately, after running docker-compose down and right after<br class="">docker-compose up, this last command resets the django container (the<br class="">container gets a new ID), and why I see that, after running docker-compose<br class="">up the templates [1] and static [2] returns to their default configuration.<br class="">[1]<br class="">https://github.com/GeoNode/geonode-project/tree/2.7/project_name/templates<br class="">[2]<br class="">https://github.com/GeoNode/geonode-project/tree/2.7/project_name/static/css<br class=""><br class="">I appreciated your time<br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class=""><br class="">On Mon, Sep 17, 2018 at 2:02 PM francesco bartoli <xbartolone@gmail.com><br class="">wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi Julierme,<br class=""><br class="">the master branch is not supposed to be always in a safe docker build, at<br class="">least until we could have time and maybe sponsors to introduce a reliable<br class="">CI/CD procedure.<br class=""><br class="">With regards to the sentence "Django container gets a new one every time<br class="">docker-compose up is run.", can you please elaborate more the issue? Is not<br class="">clear what you are facing with.<br class=""><br class="">Thanks,<br class="">Francesco<br class=""><br class="">Il giorno lun 17 set 2018 alle ore 18:52 Julierme Pinheiro <<br class="">juliermeopensourcedeveloper@gmail.com> ha scritto:<br class=""><br class=""><blockquote type="cite" class="">Hi Simone,<br class=""><br class="">I have several instances of GeoNode-Project in different VMs.<br class=""><br class="">GeoNode-Project@2.7 Docker Centos7 VM<br class="">Issue:<br class="">Django container gets a new one every time docker-compose up is run.<br class=""><br class="">GeoNode-Project@2master Docker Centos7 VM<br class="">Issue:<br class="">Related to upload layers<br class="">*Unable to<br class="">usecom.vividsolutions.jts.geom.impl.CoordinateArraySequenceFactory@32f58c5e<br class="">to produce CoordinateSequence with dimension 2*<br class=""><br class="">Thank you very much for your reply. I appreciated your time.<br class=""><br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">On Sat, Sep 15, 2018 at 5:18 AM Simone Dalmasso <<br class="">simone.dalmasso@gmail.com> wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">which version of GeoNode are you using. Keep in mind that the<br class="">geonode-project branch you use should follow the geonode's version.<br class=""><br class="">Best<br class=""><br class="">Il giorno ven 14 set 2018 alle ore 22:37 Julierme Pinheiro <<br class="">juliermeopensourcedeveloper@gmail.com> ha scritto:<br class=""><br class=""><blockquote type="cite" class="">Dear users,<br class=""><br class="">I had geonode-project@2.7 running perfectly fine, including uploading<br class="">layers. Now, I am running GeoNode-Project@master, but I am unable to<br class="">upload data layers. The following message is shown at the end of the<br class="">uploading layers process:<br class="">*Unable to<br class="">usecom.vividsolutions.jts.geom.impl.CoordinateArraySequenceFactory@32f58c5e<br class="">to produce CoordinateSequence with dimension 2*<br class=""><br class="">This would not happen on version 2.7<br class=""><br class="">Any comment on this issue would be very appreciated.<br class=""><br class="">Kind regards<br class=""><br class="">Julierme<br class=""><br class=""><br class="">_______________________________________________<br class="">geonode-users mailing list<br class="">geonode-users@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/geonode-users<br class=""><br class=""></blockquote><br class=""><br class="">--<br class="">Simone<br class=""><br class=""></blockquote>_______________________________________________<br class="">geonode-users mailing list<br class="">geonode-users@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/geonode-users<br class=""><br class=""></blockquote><br class=""></blockquote></blockquote>-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20180917/a8599a09/attachment-0001.html><br class=""><br class="">------------------------------<br class=""><br class="">Subject: Digest Footer<br class=""><br class="">_______________________________________________<br class="">geonode-users mailing list<br class="">geonode-users@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/geonode-users<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">End of geonode-users Digest, Vol 44, Issue 42<br class="">*********************************************<br class=""></div></div></blockquote></div><br class=""></div></body></html>