Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When reusing an app name, the error output shows a lot of debug statements as well #20

Open
Johannes-Werbrouck opened this issue May 4, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Johannes-Werbrouck
Copy link
Contributor

Not sure if this is a flyctl issue or not

@Johannes-Werbrouck Johannes-Werbrouck added the bug Something isn't working label May 4, 2023
@fideloper
Copy link

fideloper commented May 24, 2023

This is a fun one, I've hit it before - Laravel's .env has LOG_LEVEL=debug set in it. Laravel therefore sets LOG_LEVEL as en environment variable (via the DotEnv package that comes with Laravel). That env var gets passed down to flyctl when run via Process::run() (since parent process env vars are passed to child processes when running a command).

Then flyctl outputs a bunch of stuff - since it uses LOG_LEVEL as well by coincidence.

So one idea is to unset the LOG_LEVEL env var when calling flyctl via Process::run().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants