[GeoNode-devel] Using geonode-updateip with a custom geonode-project
simone.dalmasso at gmail.com
Thu Sep 7 23:59:48 PDT 2017
good catch, we need to fix this. I guess an approach like manage.py is
added before the import could work but needs to be tested...
Let me know
2017-09-07 18:32 GMT+02:00 Dave Kennewell <davekennewell at gmail.com>:
> Hi Geonode Devs,
> I'm using geonode 2.6.3 installed by apt-get on a fresh ubuntu 16.04
> On top of this I install geonode-project, and customise settings.py in
> This works fine if I use the postgres database that apt-get automatically
> installs locally on my geonode server.
> However, when I go to swap out this local database with a remote one (it's
> on AWS RDS), it's all good until the command "sudo geonode-updateip
> mygeonodeproject.com" tells me I don't have a superuser created (I do,
> but it's on the remote database, created using the manage.py command in
> mygeonodeproject folder).
> When I drill into this a bit deeper, it appears to come down to this line:
> This line ("from django.conf import settings") is pulling in models from
> the local geonode database, not the remote RDS database I'm using for
> What am I doing wrong here, and what is the best way to import my custom
> project into this command rather than the globally installed geonode, when
> using "from django.conf import settings"?
> thanks for any help
> geonode-devel mailing list
> geonode-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-devel