Closed livesayjesse closed 1 year ago
Hi @livesayjesse Well, the fact that you can run with the command line arguments is a good sign.... Did you close your existing command line terminals and restart after you added the environment variables? They are usually set when the window opens, and don't refresh when you add new ones....That's bitten me more than a few times. Do you see them when you echo/print them from the terminal?
I am also able to create a ".env" file on Windows without an issue... Maybe try that again? Maybe it won't create one if you have extensions hidden, or something?
Yes... So the environmental variables had reset but I also figured out how to rename the .env file. At elast for us you have to rename the file ".env." Windows will then accept the name but drop the last . lol I've never had to do that in Windows so that was new. Now it seems to be reading the .env file just fine. I love easy fixes! Thanks again!
Great!!
Hello, I'm trying to deploy STIGMan watcher in our enviornment but it seems I am stuck with using only the command line options. When I try to run the stigman-watcher-win.exe I get the following: error: required option '--api' not specified