We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Can be put behind admin auth after #17 is implemented
The text was updated successfully, but these errors were encountered:
In most of the time there is no sensitive information in sparkyd, sparky-web logs, why not make this public available ?
Sorry, something went wrong.
I think there is the config hash dump that could be sensible (not sure)
yeah, it could ... for simplicity I'd start with public facing , and with an option to disable it through a sparky global config
Great 👍
No branches or pull requests
Can be put behind admin auth after #17 is implemented
The text was updated successfully, but these errors were encountered: