shoot, i just posted about 'GeoNetwork & django-admin.py updatelayers' ... perhaps I need to revisit my settings to ensure all are synced, sorry
On Tue, Feb 15, 2011 at 5:10 PM, David Winslow <[email protected]> wrote: > Did you also change the password in GeoNetwork itself? The Django setting > doesn't change the GeoNetwork password any more than the database connection > parameters change your Postgres password. > > -d > > > On Tue, Feb 15, 2011 at 6:39 PM, Joe Larson <[email protected]> wrote: > >> I ran into a speedbump with "Postgis 2.0 failed to getBounds" - so >> reverted to installing PostGIS-1.5.2 - - only had to install >> postgresql-server-dev-8.4, libxml2-dev and GEOS from source. >> >> Loaded data into PostGIS with shp2pgsql and after activating virtual >> environment - ran "django-admin.py updatelayers >> --settings=geonode.settings". One caution: I altered the GeoNetwork >> username/password in my local_settings.py - - this gave me an issue updating >> layers, so I switched the values back to default..then it ran successfully. >> >> >> >> On Tue, Feb 15, 2011 at 7:02 AM, Ariel Nunez <[email protected]>wrote: >> >>> Joe, >>> >>> You will need to install the postgres development libraries and the >>> development libraries for GEOS and Proj4. We are installing Postgres >>> 8.4 so that should work well with PostGIS trunk. >>> >>> One thing though, every time in the past I wanted to install PostGIS >>> from sources, for one reason or the other I ended up installing GEOS, >>> Proj4 and GDAL from source too. YMMV. >>> >>> Ariel. >>> >>> On Tue, Feb 15, 2011 at 9:50 AM, Joe Larson <[email protected]> wrote: >>> > I have a geonode_prod instance going via >>> > https://github.com/jj0hns0n/chef-geonode ... I was poking around and >>> > thinking about adding PostGIS from svn - - will this build and version >>> of >>> > postgresql allow a PostGIS install? Any concerns, etc. with doing so? >>> > Thanks, Joe. >>> > >>> >> >> >
