title: Distributing Django projects with unique SECRET_KEYs
body: <p>I have a Django project that I'd like to distribute on a public repository like bitbucket or github.  I'd like it to be as easy to install as possible, so I'm including the full project, not just the pluggable apps.  This means that the <code>settings.py</code> file will be included as well.</p>
  
  <p>How can I avoid the problem of <code>settings.SECRET_KEY</code> being the same for every installation?</p>
  
  <p>Is the only <em>simple</em> solution to have the user manually modify <code>settings.py</code>?</p>
  
  <p>Should I store the key in the default database and have <code>settings.py</code> initialize it if it doesn't exist?  That would solve the problem, but I'm wondering if there is already a standard way of doing this.</p>
  
  <p>Thanks!</p>