[GeoNode-users] Don't upgrade to 2.4 without backing up your server

[Ariel Nunez]

There is a new Geoserver in the final and the package may overwrite things
in your data dir. My suggestion is to keep a copy of /usr/share/geoserver
in a safe place.

-a

On Tue, Nov 24, 2015 at 6:07 PM, Daniel Victoria <daniel.victoria at gmail.com>
wrote:

> Hi Ariel,
>
> Dumb question. And how about updating from 2.4b26 to release? Anything
> special that needs to be done?
>
> Cheers
> Daniel
>
> On Tue, Nov 24, 2015 at 1:47 PM, Ariel Nunez <ingenieroariel at gmail.com>
> wrote:
>
>> Hello all,
>>
>> We chose a different ppa (ppa:geonode/stable instead of
>> ppa:geonode/release) to prevent anyone from upgrading automatically and
>> getting any data overwritten.
>>
>> The recommended way to upgrade to 2.4 from an older version is not to
>> upgrade in place, but to either create a mirror of the existing server and
>> migrate afterwards or spin a new instance if you are using VMs.
>>
>> Some of the contributors are working on a new tool to help backup and
>> restore between different versions of GeoNode but it is not done yet. In
>> the meantime, you can use the scripts developed by NEPAnode and WFP to
>> upgrade from 2.0:
>>
>> Migration instructions
>> <https://github.com/capooti/geonode/blob/migration_from20_to_24/scripts/migrations/migrate20to24/index.rst>
>>
>> -ariel
>>
>> _______________________________________________
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20151124/6819de1b/attachment.html>