Hopefully a simple question: I have a GeoNode up, slightly customized, and running well (and I'm in love with it) on EC2. I'm hoping to implement a nearly identical setup at work using an existing PostGIS. Is the use of an existing PostGIS install as simple as editing the settings.py file, as you would with any Django install, to point at my PostGIS, or do those settings show up in more than one place? Thank you, --- Paul Bartsch PDBartsch@gmail.com
That should be it ... actually just making a local_settings.py is easier/better. Jeff On Tue, Oct 25, 2011 at 5:18 PM, Paul Bartsch <pdbartsch@gmail.com> wrote: > Hopefully a simple question: I have a GeoNode up, slightly customized, and > running well (and I'm in love with it) on EC2. I'm hoping to implement a > nearly identical setup at work using an existing PostGIS. Is the use of an > existing PostGIS install as simple as editing the settings.py file, as you > would with any Django install, to point at my PostGIS, or do those settings > show up in more than one place? > Thank you, > --- > Paul Bartsch > PDBartsch@gmail.com >
Thanks Jeff! I actually just found a great reply from you on this same topic in the librelist archives: http://librelist.com/browser//geonode/2011/9/12/use-geonodes-postgis-install/#8efc5a64a561204a04326ed86fe36589 I'll look there first next time. Thanks, Paul On Tue, Oct 25, 2011 at 5:21 PM, Jeffrey Johnson <jjohnson@opengeo.org>wrote: > That should be it ... actually just making a local_settings.py is > easier/better. > > Jeff > > On Tue, Oct 25, 2011 at 5:18 PM, Paul Bartsch <pdbartsch@gmail.com> wrote: > > Hopefully a simple question: I have a GeoNode up, slightly customized, > and > > running well (and I'm in love with it) on EC2. I'm hoping to implement a > > nearly identical setup at work using an existing PostGIS. Is the use of > an > > existing PostGIS install as simple as editing the settings.py file, as > you > > would with any Django install, to point at my PostGIS, or do those > settings > > show up in more than one place? > > Thank you, > > --- > > Paul Bartsch > > PDBartsch@gmail.com > > >
I highly recommend configuring GeoNetwork to use Postgres as well - the default embedded database is ok for development but not really intended for production. The Debian packages will configure GeoNetwork to use Postgres by default so if you are using those be aware that's another place a database connection may be specified. The database details are in webapps/geonetwork/WEB-INF/config.xml in your servlet container. -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Oct 25, 2011 at 10:09 PM, Paul Bartsch <pdbartsch@gmail.com> wrote: > Thanks Jeff! I actually just found a great reply from you on this same > topic in the librelist archives: > http://librelist.com/browser//geonode/2011/9/12/use-geonodes-postgis-install/#8efc5a64a561204a04326ed86fe36589 > I'll look there first next time. > Thanks, > Paul > > > > > On Tue, Oct 25, 2011 at 5:21 PM, Jeffrey Johnson <jjohnson@opengeo.org>wrote: > >> That should be it ... actually just making a local_settings.py is >> easier/better. >> >> Jeff >> >> On Tue, Oct 25, 2011 at 5:18 PM, Paul Bartsch <pdbartsch@gmail.com> >> wrote: >> > Hopefully a simple question: I have a GeoNode up, slightly customized, >> and >> > running well (and I'm in love with it) on EC2. I'm hoping to implement a >> > nearly identical setup at work using an existing PostGIS. Is the use of >> an >> > existing PostGIS install as simple as editing the settings.py file, as >> you >> > would with any Django install, to point at my PostGIS, or do those >> settings >> > show up in more than one place? >> > Thank you, >> > --- >> > Paul Bartsch >> > PDBartsch@gmail.com >> > >> > >