A quick solution would be to keep sensitive information in a local_settings.py file that you don't track with Git.
On Sat, Aug 4, 2012 at 4:57 PM, Schmidtchen Schleicher < spiolli...@googlemail.com> wrote: > I want to use GIT as versioning system for my Django project and as a > matter of cushiness I want to host it publicly on Github. But isn't it > dangerous to have the secret key and the database (I'm using sqlite during > development) publicly available? What can I do instead? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/GmmjkBtnc1oJ. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- Jonathan D. Baker Developer http://jonathandbaker.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
