[GeoNode-users] Migrating data and maps from Geonode 2.4 to 2.6
mpetermangis at gmail.com
Sun Jul 23 15:17:04 PDT 2017
Thanks for the help. After importing my databases from the geonode 2.4 host
to the new 2.6 host, I ran python manage.py migrate --fake-initial and it
seemed to work. However, the 2.6 host is now loading data from Geoserver on
the 2.4 host (the source for map tiles is pointing to the 2.4 host, not the
new one), and there are no layers in the local instance of Geoserver on the
How can I make Geoserver on the 2.6 host recognize the data that is loaded
On Mon, Jul 17, 2017 at 1:35 AM, Simone Dalmasso <simone.dalmasso at gmail.com>
> Hi, it is ok to restore a 2.4db into a 2.6 one because the data model
> hasn't breaking changes. the geonode command is just a wrapper around
> "python manage.py" so you can use it instead.
> 2017-07-16 3:34 GMT+02:00 Michael Peterman <mpetermangis at gmail.com>:
>> I have a production site running Geonode 2.4 that I would like to migrate
>> to 2.6 with all users, layers, and maps. I found this thread:
>> but it is a bit vague--do I simply dump the 2.4 databases from PostgreSQL
>> and restore on the 2.6 server?
>> On the 2.6 server, I did a manual installation because I want to have a
>> custom frontend. This means that the command "geonode migrate
>> --fake-initial" is not available, but is there a django equivalent? Or,
>> would it be better to install from a package using apt-get install geonode?
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-users