I'll have a look into it, strange that the binary version behafes different... as fare as I know is go run also compiled and executed...

from proxy-request-checker.

Hey @rkruetli

I'll have a look into it, strange that the binary version behafes different... as fare as I know is go run also compiled and executed...

You're right, when running the built binary from the project's root, it works. Sadly, when moving the executable proxy-checker.exe to another folder or executing it from a different path, it obviously can' find the config or report folder which is found at the project's root.
So either, running the binary from somewhere else isn't an option or we need to implement a workaround.

Success

1. Building a binary from project root

$ go build -o proxy-checker cmd/main.go

2. Executing the proxy-checker from project root, since it got saved there

$ ./proxy-checker 
2024/01/15 11:32:16 Requesting https://google.com
2024/01/15 11:32:16 Requesting https://dev.to
2024/01/15 11:32:16 Requesting https://css.ch
2024/01/15 11:32:16 Requesting https://slack.com

Fail

1. Fails when running the binary from different path then project root

$  ./go-proxy-request-checker/proxy-checker 
2024/01/15 11:38:34 Error reading json file: open config/links.json: no such file or directory. Using default values...
2024/01/15 11:38:34 Requesting https://www.google.com
2024/01/15 11:38:34 Requesting https://www.slack.com

Solution

• Export the configs on build time into the binary, meaning they can't be changed afterwards.
• Make binary request a proper config file, from a constant path, before executing (environment_variables, etc.).

from proxy-request-checker.