The ability to run bolt within a container would open the door for more usage of `bolt` in the context of "cloud native"
The container should treat {{/Boltdir}} as the project directory (which should happen by default). The user is expected to create their own image 'based on' this image that bakes their code in to that directory, or mounts it as a volume. We should document both of these workflows (though they're both common - shouldn't need too much detail).
The ability to run bolt within a container would open the door for more usage of `bolt` in the context of "cloud native" The container should treat {{/Boltdir}} as the project directory (which should happen by default). The user is expected to create their own image 'based on' this image that bakes their code in to that directory, or mounts it as a volume. We should document both of these workflows (though they're both common - shouldn't need too much detail).
The image should just have bolt and bundled content. The Bolt container is currently built on Ubuntu 16.04 image.
The ability to run bolt within a container would open the door for more usage of `bolt` in the context of "cloud native" The container should treat {{/Boltdir}} as the project directory (which should happen by default). The user is expected to create their own image 'based on' this image that bakes their code in to that directory, or mounts it as a volume. We should document both of these workflows (though they're both common - shouldn't need too much detail).
The image should just have bolt and bundled content. The Bolt container is currently built on Ubuntu 16.04 image.
Document passing inventory as an environment variable to the container.