I actually was not aware of the 'rmvirtualenv' command - I usually just delete and recreate the /var/www/geonode/wsgi/geonode/ directory entirely.
You are correct that the static media directories are not needed now; instead you should just create an Alias in apache to point at /var/www/geonode/wsgi/geonode/src/GeoNodePy/geonode/media/ . (Note of course that if you have installed in a different directory than what the documentation suggests, you will need to adjust the above paths.) -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Aug 23, 2011 at 4:14 AM, Patrick Krejci <[email protected]> wrote: > Hi David, > > thank you for your answer. Sorry but I don't have much experience with > python and virtualenv. Do I have to remove the virtual environment by > using the command rmvirtualenv (remove an existing virtualenv) to blow > the django virtualenv away? I don't want to make something wrong, so > that there will be any incompatibilities. > > I think I also have to delete all "static media" directories > (Javascript, CSS, ...), which where copied into the htdocs directory > of the geonode installation, because the new version Geonode1.1beta2 > doesn't include the static files seperatly in the download archive. > > Thanks > > -- > Patrick Krejci > > > 2011/8/22 David Winslow <[email protected]>: > > 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 > > > > > > > > -- > Patrick Krejci, M.Sc. > Wissenschaftlicher Mitarbeiter/Junior Researcher > > CEIT ALANOVA gemeinnützige GmbH > Institute of Urbanism, Transport, Environment and Information Society > Am Concorde-Park 2/F > A-2320 Schwechat > > phone +43 (0)664 85 44 392 > fax + 43 1 90360 1299 > > [email protected] > www.ceit.at > > REAL CORP 2012: 14-16 May 2012, > "RE-MIXING THE CITY/WIEDER-DURCHMISCHUNG DER STADT" > Multiversum Schwechat, Austria > www.corp.at >
