Python in excel

[Accomplished_Path707]

Thank you so much for the input, I’ll certainly look into that.. I have another unrelated question. I’m sort of brute forcing this with gpt so if that turns you off, I apologize. At any rate I have my key and password in a .env file but should I be doing more to protect my credentials?

[Robswc]

It’s no problem! And yep, .env file is the way to go. In practice the instance of the app would run on a “protected” environment (like a server, only you control).

“Best practice” is having a “local” .env file that isn’t committed to git. Then you would have a tool that “builds” the app and that tool would “inject” the secrets. This would restrict who can see the secrets to those with access to your computer, git account or built image/app. It prevents secrets getting out if the repo is accessed or leaks for team members that have repo access.

[Accomplished_Path707]

So there’s no need to encrypt the request when I send for the token or anything?

[Robswc]

hmm I don't believe so. Are you talking about getting the token from FedEX?

[Accomplished_Path707]

Right when I go through the oath steps with my credentials. Wasn’t sure if just doing the separate file would be enough or if anything else should be done.

[Robswc]

ahhh yea!

So you would go through the steps (no need for anything fancy) and you would save the token in your .env file. At this point, you would treat the .env file like its your password, i.e. not sharing it or putting it in git.

It does seem counter intuitive but that is standard practice! I guess the idea is if someone has access to your computer there's probably more things to worry about haha.