[GeoNode-users] GeoNode Project master Docker - Upload layers

Julierme Pinheiro juliermeopensourcedeveloper at gmail.com
Mon Sep 17 10:37:42 PDT 2018


... their default configuration [1] and [2]

Kind regards

Julierme

On Mon, Sep 17, 2018 at 2:36 PM Julierme Pinheiro <
juliermeopensourcedeveloper at gmail.com> wrote:

> Hi Francesco,
>
> Thank you very much for your reply. I have GeoNode-Project at 2.7 installed
> via Docker in a Centos7 VM and I had edited the templates html (site_base
> and site_index) and css file (site_base). GeoNode site was working
> smoothly. But lately, after running docker-compose down and right after
> docker-compose up, this last command resets the django container (the
> container gets a new ID), and why I see that, after running docker-compose
> up the templates [1] and static [2] returns to their default configuration.
> [1]
> https://github.com/GeoNode/geonode-project/tree/2.7/project_name/templates
> [2]
> https://github.com/GeoNode/geonode-project/tree/2.7/project_name/static/css
>
> I appreciated your time
> Kind regards
>
> Julierme
>
>
> On Mon, Sep 17, 2018 at 2:02 PM francesco bartoli <xbartolone at gmail.com>
> wrote:
>
>> Hi Julierme,
>>
>> the master branch is not supposed to be always in a safe docker build, at
>> least until we could have time and maybe sponsors to introduce a reliable
>> CI/CD procedure.
>>
>> With regards to the sentence "Django container gets a new one every time
>> docker-compose up is run.", can you please elaborate more the issue? Is not
>> clear what you are facing with.
>>
>> Thanks,
>> Francesco
>>
>> Il giorno lun 17 set 2018 alle ore 18:52 Julierme Pinheiro <
>> juliermeopensourcedeveloper at gmail.com> ha scritto:
>>
>>> Hi Simone,
>>>
>>> I have several instances of GeoNode-Project in different VMs.
>>>
>>> GeoNode-Project at 2.7 Docker Centos7 VM
>>> Issue:
>>> Django container gets a new one every time docker-compose up is run.
>>>
>>> GeoNode-Project at 2master Docker Centos7 VM
>>> Issue:
>>> Related to upload layers
>>> *Unable to
>>> usecom.vividsolutions.jts.geom.impl.CoordinateArraySequenceFactory at 32f58c5e
>>> to produce CoordinateSequence with dimension 2*
>>>
>>> Thank you very much for your reply. I appreciated your time.
>>>
>>> Kind regards
>>>
>>> Julierme
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Sep 15, 2018 at 5:18 AM Simone Dalmasso <
>>> simone.dalmasso at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> which version of GeoNode are you using. Keep in mind that the
>>>> geonode-project branch you use should follow the geonode's version.
>>>>
>>>> Best
>>>>
>>>> Il giorno ven 14 set 2018 alle ore 22:37 Julierme Pinheiro <
>>>> juliermeopensourcedeveloper at gmail.com> ha scritto:
>>>>
>>>>> Dear users,
>>>>>
>>>>> I had geonode-project at 2.7 running perfectly fine, including uploading
>>>>> layers. Now, I am running GeoNode-Project at master, but I am unable to
>>>>> upload data layers. The following message is shown at the end of the
>>>>> uploading layers process:
>>>>> *Unable to
>>>>> usecom.vividsolutions.jts.geom.impl.CoordinateArraySequenceFactory at 32f58c5e
>>>>> to produce CoordinateSequence with dimension 2*
>>>>>
>>>>> This would not happen on version 2.7
>>>>>
>>>>> Any comment on this issue would be very appreciated.
>>>>>
>>>>> Kind regards
>>>>>
>>>>> Julierme
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> geonode-users mailing list
>>>>> geonode-users at lists.osgeo.org
>>>>> https://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>>
>>>>
>>>>
>>>> --
>>>> Simone
>>>>
>>> _______________________________________________
>>> geonode-users mailing list
>>> geonode-users at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/geonode-users
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20180917/a8599a09/attachment.html>


More information about the geonode-users mailing list