I run the Whats-up-docker with 21 triggers, all set for individual containers.
I am not interested in using one compose file, because I don't want to ctrl find my way in a huge stack. I do have stacks for more complicated apps (like a TIG stack - Telegraf, Influxdb and Grafana) but that is about it.
When I fire the wud up I get this error:
(node:6) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 wud:container-reports listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ... to show where the warning was created)
I have kept the log level on debug but haven't found something usefull in the wud.json.
I think your application is great and very usefull all arround and it was not clearly designed for this kind of env abuse on multiple triggers, but I hope you would make it more friendly to beginners that start up with one project per directory and don't want to use a huge stack.
The app would serve me well even with no update whatsoever, but triggering small updates like patch and leave the major ones to manual is very appealing. Triggering a pull, down and up -d with a manual trigger from UI would also be very nice.
Also I don't see the wud.link.template in the wud UI on the containers listed with updates. I presume they show in notifications but they really should also be visible on the UI on the update tab. Letting us at least specify a link to the changelog would be very, very good.
Other random thoughts:
using a trigger name with an underline completely breaks the trigger:
WUD_TRIGGER_DOCKERCOMPOSE_PLEX_UPDATE_FILE (this would not be parsed by wud,)
the documentation is lacking when dealing with docker-compose
Hello,
I run the Whats-up-docker with 21 triggers, all set for individual containers.
I am not interested in using one compose file, because I don't want to ctrl find my way in a huge stack. I do have stacks for more complicated apps (like a TIG stack - Telegraf, Influxdb and Grafana) but that is about it.
When I fire the wud up I get this error:
(Use
node --trace-warnings ...
to show where the warning was created)here is my compose file:
I have kept the log level on debug but haven't found something usefull in the wud.json.
I think your application is great and very usefull all arround and it was not clearly designed for this kind of env abuse on multiple triggers, but I hope you would make it more friendly to beginners that start up with one project per directory and don't want to use a huge stack.
The app would serve me well even with no update whatsoever, but triggering small updates like patch and leave the major ones to manual is very appealing. Triggering a pull, down and up -d with a manual trigger from UI would also be very nice.
Also I don't see the wud.link.template in the wud UI on the containers listed with updates. I presume they show in notifications but they really should also be visible on the UI on the update tab. Letting us at least specify a link to the changelog would be very, very good.
Other random thoughts: using a trigger name with an underline completely breaks the trigger:
WUD_TRIGGER_DOCKERCOMPOSE_PLEX_UPDATE_FILE (this would not be parsed by wud,)
the documentation is lacking when dealing with docker-compose
ps: thank you for your effort, your app is great!