> 2 cents -- My gut is +1 on separating out the local_settings but I have two > questions: > (1) What is the criteria for determining whether a settings should go in > local_settings vs. general site settings?
Generic GeoNode settings should be in settings.py, they should work for a developer machine and be able to run even if local_settings.py is not defined. Only the specific bits for a given deployment, like [DATABASE_NAME, SITE_URL, GEOSERVER_BASE_URL, EMAIL_HOST, ADMINS] should be in local_settings, we should provide users for a sample of a LOCAL_SETTINGS file with commented out options and explanations about them. > (2) How would this would work with the make_release process and the > resulting bundle. The same steps we take to safeguard the production.db file should be taken to keep the local_settings.py file both private and backed up. For instance, In my server I have a ~/local dir that contains the local_settings.py, the sqlite db and the paster .ini file and I keep them on a private github repo. I use symlinks to put them in the right places of the filesystem. > (3) What should the default deployment options be for the source code/build? Not sure how to answer this, I don't understand the question. Ariel
