You need to protect those secrets, and that isn't covered here. Encryption should be applied to the file contents, and restrictive ACLs should be applied to the file itself.
@robertcenusa86365 ай бұрын
Could you recommend a tutorial that covers that part?
@SkielCast Жыл бұрын
Some observations: - The value of __name__ should not be use to determine environments - To choose between environments, an additional environment variable called "environment" could be used, with a default value of "dev" to avoid errors - Having multiple .envs in local could make sense but only as an edge case, production credentials should not be in ANY local machine - If Python-dotenv is going to be a dependency, considered using tools like PDM, Poetry or Pipenv to make sure dependencies are locked
@mycinemax2653 Жыл бұрын
if i put .env or separate file to save secrets in my working server, how I protect it from outside hacker?
@zen.ali2387 ай бұрын
did you find the answer?
@ElenaBiriuchevskaia8 ай бұрын
Thank you! Very well explained!
@andrewschneider5722 Жыл бұрын
So if the secrets aren't in git, how can other collaborators use the secrets if they pick up a story that uses this code or how do testers test this code if they can't access the secrets?
@linux_fr10 ай бұрын
Secret Manager
@shubhamtarkar38 Жыл бұрын
Hi can you make a tutorial on implementing Ci-Cd with bitbucket and ggshield
@infossil8 ай бұрын
thank you, excellent
@hughesadam87 Жыл бұрын
Where does keyring fit into all this?
@lxvi43228 ай бұрын
how can I use this inside Aws Services like ERM-Studio? tnx
@GitGuardian8 ай бұрын
You might want to try using AWS secrets manager for AWS native environments kzbin.info/www/bejne/l6SXmIqghr6lfsUsi=v8-fL7fkpw3lJQGE
@mrs.neerajsharma799711 ай бұрын
Thank you so much , u r awesome
@GitGuardian11 ай бұрын
Thanks for the feedback!!!
@mohammediftekharsalam82554 ай бұрын
Bro I am seeing this video on a Tuesday coincidentally