将字符串替换为空字符串的特殊字符(Replace string with special characters for empty string)

 虽然这是一种常见的方法，但这不是一个好方法。 我过去曾使用过这种配置，因此放弃了它。 当您有多个开发人员一起工作或部署到多个环境（即分段和生产）时，问题就出现了。 您可以选择其中之一 
 
 
 
 make settings.py生产设置。 然后，每个开发人员必须覆盖设置以设置其本地环境（数据库设置， DEBUG=True ，添加debug_toolbar等）。 由于这不是源代码控制，它是重复工作，并导致“它在我的机器上工作”的各种问题。 
 
 
 make settings.py开发设置。 现在，您在local_settings.py拥有有意义的生产配置部分，这些部分不在源代码管理中 。 这使部署变得混乱。 显然，您不希望将敏感信息放在源代码管理中。 
 
 
 添加暂存环境只会让情况变得更糟。 我更喜欢SplitSettings wiki中描述的简单包环境组织 。 

While this is a common approach it is not a good approach. I have used this type of configuration in the past and since abandoned it. The problem comes when you have multiple developers working together or when you are deploying to multiple environments (i.e. staging and production). You have the choice of either
 
 
 
Make settings.py the production settings. Then each developer must override settings to setup their local environment (DB settings, DEBUG=True, adding debug_toolbar, etc). Since this is not in source control it is repeated work and leads to "it works on my machine" kinds of problems.
 
 
Make settings.py the development settings. Now you have meaningful pieces of your production configuration in local_settings.py which is not in source control. This makes deployment messy. Obviously you don't want to put sensitive information in the source control. 
 
 
Adding a staging environment just makes this worse. I much prefer the Simple Package Organization for Environments described in the SplitSettings wiki.