1) I don't see anything related to this in the diff. What needed to be changed to run the site with geonode.settings?
2) Looking over the diff for this I saw some stuff (like viewer.json) that can be dropped entirely instead of ported. 3) Why is this needed? 4) This needs some discussion before pulling into master, as I guess it will become the endorsed means of customizing a GeoNode site if we bring it in. -d On Wed, Aug 11, 2010 at 11:38 AM, Ariel Nunez <[email protected]>wrote: > Hi people, > > I made a few updates to GeoNode while doing the deployment on the > Bank's Amazon Instance. > > The can be found in this branch: > http://github.com/ingenieroariel/geonode/compare/master...deploy > > And here is a summary: > > 1. Fixed the codebase to run the website using geonode.settings > instead of capra.settings > 2. Removed mentions of CAPRA wherever possible > 3. Added a new setting called SERVE_MEDIA indicating if Django should > serve media or not. Before that we used the DEBUG value. > 4. Added a local_settings import to separate deployment options from > the main settings file. (We need to create a sample_local_settings.py > for people to start off) > > I would like some feedback about those changes to see if I can merge > that branch into master. > > Cheers, > Ariel > > PD: I plan to both send another email with bugs(after I ticket them) I > found while deploying and also write up a document about deploying > GeoNode in Ubuntu that will cover setting up Nginx as a frontend > proxy, enabling registration, adding an Email backend, adding custom > templates to override GeoNode ones (for html/css savvy users). >
