On Wed, Aug 11, 2010 at 11:05 AM, David Winslow <[email protected]> wrote: > 1) I don't see anything related to this in the diff. What needed to be > changed to run the site with geonode.settings?
Moving the registration templates from the capra dir to the geonode one. > 2) Looking over the diff for this I saw some stuff (like viewer.json) that > can be dropped entirely instead of ported. Which other files can be dropped apart from that one? > 3) Why is this needed? This is a pony, just a way to have more control over the behavior of the media serving within Django, specifically in deployment I never want to serve files with Django, but I want to be able to set DEBUG on sometimes to see the fancy error page. It is also the same setting used in the static files app used in Pinax: http://pinaxproject.com/docs/dev/settings.html#serve-media > 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. This is the defacto way to customize a Django project, it is used by Satchmo, Pinax, Django Mingus and many others. As it stands we would need to choose between importing a local_settings.py from the main settings file or creating another settings file and importing geonode's settings at the start. I like the local_settings.py approach because I can choose to put some code after that import to reuse the update vars (for example the media links at the end of the settings file). The local_settings.py file should be kept outside version control, and sensible information like database password, email password, etc should be there. Ariel
