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

HealthCheck Suggestion #490

Closed
capncybo opened this issue Nov 25, 2024 · 3 comments
Closed

HealthCheck Suggestion #490

capncybo opened this issue Nov 25, 2024 · 3 comments

Comments

@capncybo
Copy link

capncybo commented Nov 25, 2024

Thanks Sigoden, I Absolutely LOVE your DUFS software.
Very much appreciated!!!

Perhaps your intent was ONLY for local server verification
[Note: I previously missed the (example) being ONLY the local loopback address 127.0.0.1]
Ex)
curl http://10.19.38.66:50000/__dufs__/health
{"status":"OK"}

And Re-reading it now... (It makes complete sense to me).
However, while previously tinkering around (with some other simple bash scripts) I was thinking perhaps something like...
Ex)
curl http://10.19.38.66:50000/__dufs__/health?simple
OK

Might be nice, & probably easy for you to implement.
Although I do understand... Almost any response should indicate the server is up & online...
So, I'm no longer sure of the validity of my ask, LOL

@sigoden
Copy link
Owner

sigoden commented Nov 25, 2024

dufs already supports the health api #474

@sigoden sigoden closed this as completed Nov 25, 2024
@capncybo
Copy link
Author

Thanks BUT, what I meant was... for DUFS to answer the HealthCheck in a simple format.
NOT just the already existing reply in json format.
But only If you append: "?simple" to the URL
Ex)
curl http://10.19.38.66:50000/__dufs__/health**?simple**
OK

@sigoden
Copy link
Owner

sigoden commented Nov 26, 2024

We will not support this feature.

Just check if the value is {"status":"OK"} or contains OK (grep OK).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants