No, you should take care to remove the previous version of GeoServer,
GeoNetwork, and the Django app before installing the new one.  Otherwise you
may have multiple versions of dependencies around and confusing errors can
occur as the system just sort of "picks one" arbitrarily at run time.

You should have some configuration changes in (tomcat
webapps)/geoserver/WEB-INF/web.xml and (django
virtualenv)/src/GeoNodePy/geonode/local_settings.py, make sure to hang on to
those as well as the GeoServer datadir and Django database.  Then blow away:

   - (tomcat webapps)/geoserver
   - (tomcat webapps)/geonetwork
   - the django virtualenv

And re-run the relevant parts of the setup process (sorry, we don't have
this written up well.  Patches to the documentation are welcome though!)

If you put everything in the same place you should be able to reuse the
Apache configuration.

--
David Winslow
OpenGeo - http://opengeo.org/

On Mon, Aug 22, 2011 at 3:35 AM, Patrick Krejci <[email protected]> wrote:

> Hi everybody,
>
> I sucessfully installed the version Geonode 1.0 on a Ubuntu 10.04.
> Server, but I'm thinking to upgrade this version to the newest Geonode
> 1.1. beta2. I deployed the project with the installation manual
> (Deploying on Ubuntu 10.04).
> I read a post from David on the geonode.org news, that no migration is
> needed for existing sites, because the database structure reamains
> unchanged. I did a backup of my GeoServer folder to allow downgrades
> as the post said.
>
> But what is the best way to upgrade it? Shall I redeploy the new
> war.files on the tomcat without removing the previous files and should
> I copy the new django files (bootstrap, pavement, geonode-webapp) in
> the same directory and run the new bootstrap.py or is it better to
> remove all files before starting the installion and how should I do
> that?
>
> Thanks
>
> --
> Patrick Krejci
>

Reply via email to