I'm new to all of this as I'm sure you've gathered by all of my recent posts. As I'm digging deeper into Django I'm really loving and appreciating Mezzanine and its included fabfile. But I have yet another question:
What are the best practices regarding DEPLOY SETTINGS? These are the two approaches that I'm aware of: 1. In Josh's tutorial <http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/>the FABRIC dictionary from settings.py is copied to local_settings.py, uncommented, and filled in with production settings. One is further instructed to add ALLOWED_HOSTS to deploy/live_settings.py. But, live_settings.py was renamed recently and I'm able to successfully deploy a site with this method by adding ALLOWED_HOSTS to local_settings.py and configuring my production database in the same file. 2. In Ken's tutorial<http://bscientific.org/blog/mezzanine-fabric-git-vagrant-joy/>the FABRIC dictionary is uncommented in settings.py and filled in with production values, but copied to local_settings.py for use with Vagrant. I prefer this approach because I can keep my local settings separate from my production settings. The error I encounter with this approach is that when I run any manage.py or fab command my SECRET_KEY variables are called before they are imported in the following section # LOCAL SETTINGS #. Do I copy/paste SECRET_KEYs from local_settings.py or generate a new one for settings.py? Following this approach,do I comment out the FABRIC dictionary when I'm developing even after deployment in order to use my local database? And what do I do about local_settings.py? What's the best approach? Any help is greatly appreciated. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
