Tom Duffield

I'd throw programmatic registration of all notifications would be fantastic. For me, Slack would be great!

chef-init does not connect to the chef server - the chef-client does. If you are running a container based on an image that has already been converged then chef-init will...

chef-init ALWAYS runs runsvidr. That is the Supervisor that is being referenced. The chef-client run is failing because of http://docs.getchef.com/containers.html#credential-management. The service you outline in the first-boot.json will only start...

To address your first point, that is a very opinionated point of view about how that instance should behave. I understand that is how you'd like the build to work...

Thanks @ndobson for the PR. However this change hard codes a path that is specific to a Delivery Builder (/var/opt/delivery/workspace). Users can (and do) run delivery-truck outside of a Delivery...

I think the right answer is to create the file referencing the key and node name like you have above.

So there is a slightly more fine-grained workaround. Rather than running `initFlowbite`, you can call the specific init function for the component you need. For example, for me it was...