From the course: Secure Coding in Python

Unlock the full course today

Join today to access over 22,700 courses taught by industry experts or purchase this course individually.

The Django settings module, keeping secrets, and the dangers of debug mode

The Django settings module, keeping secrets, and the dangers of debug mode - Python Tutorial

From the course: Secure Coding in Python

Start my 1-month free trial

The Django settings module, keeping secrets, and the dangers of debug mode

“

- [Teacher] As soon as we begin working on a project, we want to become conscientious of what goes into source control and what doesn't. While access to source control is usually restricted, these restrictions can at times be compromised and we want to minimize the consequences of such a compromise. Further, not every individual with access to source control, should automatically have access to everything. Here's an example of that. So here I am at 03/03_04_begin/feed, and if I type in ls to see what's here, you'll see that there is the secret_key.txt. You'll remember that we've removed this out of source code and into its own file, just to keep this out of source control. So if we were to commit it at this point, that would sort of defeat the purpose. The way to keep this out of source control would be to establish a gitignore file. Clear the terminal, and I'm going to head over to my code editor, and here, in the base…

Contents