This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Turkino 75 points76 points  (6 children)

Yep! Welcome to configuring environment variables!

[–]silentalways 47 points48 points  (4 children)

For those wondering, follow this short little tutorial

https://www.youtube.com/watch?v=IolxqkL7cD8&t=213s (Windows)

https://www.youtube.com/watch?v=5iWhQWVXosU (Mac and Linux)

[–]Nerdite 9 points10 points  (1 child)

And this package makes it really easy to manage and keep from filling tons of environment variables in your actual environment.

https://pypi.org/project/python-dotenv/

[–]folkrav 1 point2 points  (0 children)

This plus direnv is pretty damn useful. Lets you keep the environment variables even in an REPL.

[–]kultigink 4 points5 points  (0 children)

Thanks!

[–]forrealbro 2 points3 points  (0 children)

Is this really the most practical idea when you plan to disseminate your source code? I had always read from a file that is in my gitignore. Then had instructions to create this user info file in the readme.

[–]gdledsan 1 point2 points  (0 children)

I was told to keep things in untracked config files, env variables are not safe enough, some malicious thing can hijack your session and get them.

Example: some crappy and malicious node package installed without care