I'd like to have one file with configurable settings instead of having these settings spread out over mulitple models and controllers. What's the best practise for this?
My solution is to create a '_settings.py' model. I prepended it with an underscore to ensure it is the first excuted model file. This way the settings in it can be used by other model files, most notable db.py. This works under OS X, though I am not sure if this is a cross platform safe way to ensure _settings.py is actually loaded first. Reason for not simply including all settings in db.py is that I do want to check in db.py in my DVCS, but not the settings such as DB password, password of the SMTP user, and other potentially sensitive information. Thoughts? -- Guido Kollerie -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
