Replies: 1 comment
-
|
As a standalone tool, sure, I have no problem with that! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Howdy! First - thanks for this, it's awesome!
I can't be the only one that has a "one monitor per service" situation, so it would be really handy if I could describe the gatus requirements in docker labels.
This could either be built into gatus itself, or as a stand alone tool which I could optionally deploy alongside gatus which did the magic "notice gatus docker labels and build config accordingly".
This would avoid the cycle of "new service, add config to caddy, add config to gatus" to "new service including gatus docker labels, add config to caddy" :-). (Yes, I know caddy supports labels too).
WDYT?
Beta Was this translation helpful? Give feedback.
All reactions