For the database you can set your git ignore to ignore your database, or store it in a separate path and use git there for that specifically.
For your secret key, use the git hook pre committing to change that line, storing the key outside of your project so you don't lose it. Use the post commit hook to put your key back from wherever you stored it, maybe an ignored temp file. The post commit hook could also be used to commit any db changes if you do what I said above about moving the db somewhere else. On Aug 4, 2012 6: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. > -- 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.
