Cannot use .env to set secrets, the superseded method is insecure
the create secrets (as i understand it) allow others to use your api keys to run your programs. I do not want this behaviour, i want to create a .env that allows the code to be public but each user must use their own key. Im not funding someone elses openai calls.
It is actually the opposite, replit secrets only let you use it, if someone else runs your repl the secret will not be availabile. It is exactly like .env but instead of a text file it give you a GUI
I dropped into shell and created a .env when i was blocked. Being an “old school” programmer i learned the original Klingon version of Python, called COBOL. so when blocked, i go to cli.
now do i now get rid of the .env in favor of the correct method. It still exists, my keys are still available but rm .env doesnt find it, nor does ls -a
There is no .env, and pid1 (the init process Replit runs in repl Docker containers) will delete any .env files you create. You don’t need to get rid of it or anything