You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a comment on what I'm seeing but the default behavior of ubbagent-start is to disable HTTP access unless a port is provided. I would expect port 3456 to be used as the default (or whatever you choose).
Additionally, it's undocumented and unclear what this application should do at all if HTTP is disabled. Suggest defaulting to port 3456 and always enabling HTTP unless explicitly disabled by configuration (in the event that's useful)
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. It's possible to have the agent auto-report at predefined intervals (i.e., to report only usage time), at which point the HTTP interface isn't strictly necessary. Although even in this case, we still recommend monitoring its /status endpoint.
I'd rather not prescribe a default port. What about another option: require the port parameter, and allow it to optionally be set to "disabled" to explicitly disable the HTTP interface.
I think most of the time what the port is won't matter if this is in the sidecar, I can't imagine it conflicting with much else. It's not really something I'd even have much opinion about, which is why I was thinking it makes sense to have a default.
Admittedly this is preference; it's nice to have tools that do something sensible in the default without much configuration, but that allow control on the elements you care enough to change. I like to avoid making decisions that don't much matter to my development process, and delegate those to the original author, I have enough decisions to make. :)
All of that being said, it's kind of a minor point, hardly a dealbreaker as long as it's clear either way.
Just a comment on what I'm seeing but the default behavior of
ubbagent-start
is to disable HTTP access unless a port is provided. I would expect port3456
to be used as the default (or whatever you choose).Additionally, it's undocumented and unclear what this application should do at all if HTTP is disabled. Suggest defaulting to port 3456 and always enabling HTTP unless explicitly disabled by configuration (in the event that's useful)
The text was updated successfully, but these errors were encountered: