-
Notifications
You must be signed in to change notification settings - Fork 3
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
Default config for non heroku environments #59
Comments
Hey @jasonsbrooks, Thanks for this bug report. I'm able to reproduce this locally and I'm going to patch this today. |
Awesome, thanks so much @karls ! |
karls
added a commit
that referenced
this issue
Apr 27, 2023
karls
added a commit
that referenced
this issue
Apr 28, 2023
* Fix detecting if Judoscale should report metrics. Fixes #59 * Update sample apps
Hey @jasonsbrooks, I've just released 1.4.1, which should fix the issue you're seeing. 🙌🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The default config for non Heroku environments is currently set as follows:
judoscale-python/judoscale/core/config.py
Line 53 in e101123
so
API_BASE_URL
is set as an empty string.The code that determines if Judoscale should run, though, seems to compare
API_BASE_URL
againstNone
:judoscale-python/judoscale/django/apps.py
Line 20 in e101123
We've been seeing Judoscale attempting to run locally on our dev machines, and pretty sure it's because this check is returning True.
Should the default config instead return
return cls(None, None, env)
so theAPI_BASE_URL
is set to None instead of ""? Or alternatively should the check beif judoconfig["API_BASE_URL"]:
? Happy to put up a pull request if this seems reasonable.The text was updated successfully, but these errors were encountered: