Hi David, Many thanks. I think I have this working, but only if I load jetty and paster separately. I'm still trying to track down why running paver host doesn't work. However, I have hit a big gotcha in that a lot of my data stores in my main geoserver installation have spaces in their names, and this is causing geonode to fail when I update the layers.
On a slightly separate issue, when I run jetty and paster separately, I encounter some out of memory errors when loading data into geonode (this is from before I configured it to work with a remote geoserver instance). I have changed the settings for jetty, but these still occur. However, when I call them together using paver host, I don't get the out of memory errors. Unfortunately, if the jetty load times out because it has a lot of updates to do, then this causes errors- and also I have the problem noted above when running it in this way... I'm happy to provide more information on these things if you can tell me which logs you need and where to find them. Thanks Jo ----- Original Message ----- From: "David Winslow" <[email protected]> To: [email protected] Sent: Tuesday, 21 September, 2010 2:07:02 PM Subject: Re: [geonode] Questions The paster/Django portion of GeoNode communicates with GeoServer exclusively over HTTP. So jetty must be running when you run the django-admin.py command. Additionally, the Django application must be running in order to provide GeoServer without authentication information. (That is, both paster and jetty must be running when you use the admin command.) The updatelayers command only imports layers, it does not remove existing ones, so your existing test layers will not be overwritten. -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Sep 21, 2010 at 6:15 AM, Joanne Cook < [email protected] > wrote: Thanks David, So to confirm I have understood this correctly- I would change GEOSERVER_BASE_URL in src/geonode/settings.py, run the django-admin.py command as below, then start geonode without jetty, using paster serve --reload shared/dev-paste.ini? Would this overwrite existing test layers that I have loaded into geonode (I am quite happy for it to do that)? Jo ----- Original Message ----- From: "David Winslow" < [email protected] > To: [email protected] Sent: Monday, 20 September, 2010 5:29:22 PM Subject: Re: [geonode] Questions Once GeoNode is installed, the update script is integrated into the Django administration tool. You can invoke it like so: $ django-admin.py updatelayers --settings=geonode.settings Currently GeoNode only supports syncing with one GeoServer instance this way. Hope this helps. -- David Winslow OpenGeo - http://opengeo.org/ On Mon, Sep 20, 2010 at 12:13 PM, Joanne Cook < [email protected] > wrote: Hi All, I met some of you at FOSS4G a few weeks ago, and also attended the tutorial on SDI best practices with Geonode. In that, someone (Sebastian?) mentioned being able to connect Geonode to a remote Geoserver instance, and run a script to get Geonode up to date with the Geoserver layers. Can someone give me some more information on where I might find this script? Thanks Jo -- ----------------------------------------------------- Joanne Cook Senior IT Support and Development Oxford Archaeology (North) 01524 880212 http://thehumanjourney.net ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. -- ----------------------------------------------------- Joanne Cook Senior IT Support and Development Oxford Archaeology (North) 01524 880212 http://thehumanjourney.net ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. -- ----------------------------------------------------- Joanne Cook Senior IT Support and Development Oxford Archaeology (North) 01524 880212 http://thehumanjourney.net ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.
