December 13, 201411 yr Would anyone else think its beneficial to have a "reset" button next to the on/off for each container?
December 13, 201411 yr Would anyone else think its beneficial to have a "reset" button next to the on/off for each container? What does a "reset" do?
December 13, 201411 yr Author Would anyone else think its beneficial to have a "reset" button next to the on/off for each container? What does a "reset" do? basically cycle a stop/start I have few dockers that I edit the conf files directly and changes aren't seen until the docker turns off/on again.
December 13, 201411 yr Would anyone else think its beneficial to have a "reset" button next to the on/off for each container? What does a "reset" do? basically cycle a stop/start I have few dockers that I edit the conf files directly and changes aren't seen until the docker turns off/on again. It would be better to have a file watcher inside the dockers where you need this that restarts the main process it's running when it detects changes.
December 13, 201411 yr Author Would anyone else think its beneficial to have a "reset" button next to the on/off for each container? What does a "reset" do? basically cycle a stop/start I have few dockers that I edit the conf files directly and changes aren't seen until the docker turns off/on again. It would be better to have a file watcher inside the dockers where you need this that restarts the main process it's running when it detects changes. That sounds like a much more intelligent way. Two examples that pop in my head are apache and ddclient. Ninja Edit: Do you feel inotifywait would be a good way of implementing that?
Archived
This topic is now archived and is closed to further replies.