[GeoNode-devel] `updatelayers` doesn't work as expected

[EFTAS Fabian Wilske]

It turned out that DATABASE_URL and GEODATABASE_URL were not set in my 
Docker environment. Setting these environment variables to the 
appropriate values did the trick.

As someone else suggested in a previous posting, adressing the same 
problem, this can be done by executing `source $HOME/.override_env` 
prior to calling the Django admin command 
(http://osgeo-org.1560.x6.nabble.com/Command-updatelayers-and-createsuperuser-in-docker-compose-td5393949.html).

Am 18.09.2019 um 14:02 schrieb EFTAS Fabian Wilske:
> Dear all,
>
> I wanted to use `python manage.py updatelayers` to register a new layer
> I just added to GeoServer. And although `updatelayers` seems to work as
> expected and created the layer in GeoNode:
>
> root at 1eefe99ee2d8:/usr/src/app# python manage.py updatelayers -w geonode
>
> ==============================================================
> ... Creating Default Resource Links for Layer
> [geonode:2018_namibia_dbh_csir_2019_09_09]
> ... Creating Thumbnail for Layer [geonode:2018_namibia_dbh_csir_2019_09_09]
> [created] Layer 2018_namibia_dbh_csir_2019_09_09 (11/11)
>
>
> Finished processing 11 layers in 47.0 seconds.
>
> 1 Created layers
> 10 Updated layers
> 0 Failed layers
> 4.270000 seconds per layer
> root at b71e0fd2fd4f:/usr/src/app#
> ==============================================================
>
>
> ...the layer doesn't appear in GeoNode, for no user.
> I can even see the correctly created GeoFence data rules in GeoServer.
>
> Any suggestions what went wrong here?
>
> I'm using geonode/latest from Jul 26 after commit
> e217ac3eb7f461240a3e1f219258daf8be7cef63
>
> Cheers,
> Fabian
> _______________________________________________
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-devel
>