Now that I've been developing this for awhile, I figure I had a good sense of how I develop/deploy:
I've made a few helpers in bin, so I can exec hass inside the running container, so I can run bin/homeassistant --script check_config to validate changes before restarting hass.
I tended to run docker-compose up home-assistant, and would control-c to stop, and use history to start it up again.
I've combined these, plus one other feature. Instead of running docker-compose up home-assistant directly, I run docker-compose up -d home-assistant, and then attach to the newly running component. That gives me logs, while control-c doesn't actually kill it. The next time script/deploy runs it handles stopping it first.
Now that I've been developing this for awhile, I figure I had a good sense of how I develop/deploy:
I've made a few helpers in
bin, so I can exec hass inside the running container, so I can runbin/homeassistant --script check_configto validate changes before restarting hass.I tended to run
docker-compose up home-assistant, and would control-c to stop, and use history to start it up again.I've combined these, plus one other feature. Instead of running
docker-compose up home-assistantdirectly, I rundocker-compose up -d home-assistant, and then attach to the newly running component. That gives me logs, while control-c doesn't actually kill it. The next timescript/deployruns it handles stopping it first.