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
Hello,
Thank you for your awesome idea!
It would be nice to have some variables passed on to the message (like for example docker host hostname).
This would make us avoid putting a long and descriptive name to the container itself.
The text was updated successfully, but these errors were encountered:
Mmm. This could work too for docker hostname only
What I would prefer to do is to extract more data from the event to display or from the container suffering the respective event rather than pushing static env var into the node container.
Like for example, container name would be more important than the container hostname (which is the container id).
Assuming you are using fig, you could further extract from the container name the project, not only the container name.
Things is i have to knowledge on node.js so I was just thinking that your idea can be a bit extended to enable users of this container to display more infos without actually change the node app.
Hello,
Thank you for your awesome idea!
It would be nice to have some variables passed on to the message (like for example docker host hostname).
This would make us avoid putting a long and descriptive name to the container itself.
The text was updated successfully, but these errors were encountered: