Changing the docker-compose file in a livepush session will not cause a full rebuild

[CameronDiver]

As anything could have changed, this should cause a full rebuild to occur, without having to ctrl+c and restart the process.

---

Please keep in mind that we try to use the issue tracker of this repository for specific bug reports & CLI feature requests. General & troubleshooting questions are encouraged to be posted to the balena forums, which are monitored by balena's support team and where the community can both contribute and benefit from the answers.

Before submitting this issue please check that this issue is not a duplicate. If there is another issue describing the same problem or feature please add your information to the existing issue's comments.

[Hades32]

@pdcastro do you think it's sufficient to just restart the complete livepush session when we detect a change to the compose file? Or is there something we could do better than basically automating CTRL-C+restart?

[pdcastro]

@Hades32, in truth I am not familiar enough with the livepush codebase to be able tell without some deep investigation. If you are planning to fix this issue, I suppose you will familiarise yourself with it better than me. :-) The only thing I would suggest is that you have a look at how livepush current treats changes to the Dockerfile(s). And when you say "basically automating CTRL-C+restart", hopefully you don't literally mean exiting the CLI process and/or creating a CLI subprocess. :-)

cc @srlowe in case he has anything to add.

[Hades32]

haha, no no, definitely not literally doing that 😂

[CameronDiver]

The ideal situation here is to re-run all intialisation that livepush performs for a given project when the docker-compose changes. There's no need to end the process, but re-parsing the docker-compose, all Dockerfiles etc is necessary.