Frank Sachsenheim

it'd be also great if envplate would read from stdin: ``` cat templates/foo.conf | ep -d > /etc/foo.conf ``` however, `-d` seems redundant in this case.

loĺ, i just wanted to ask you for an example. :-)

in a nutshell, the idea was to preserve the contents of an instance by default, as i don't expect anyone wants to lose any customization. so, to update the Drupal-version...

> another idea was to add an ONBUILD-statement that reads a list of modules to be installed from a modules.txt. bs, that would happen after the initial `drush site-install`.

what about `docker exec`? you can also change the entrypoint and call `entrypoint.sh` from there. i haven't tested updating a module from the webinterface, but installing a module works, so...

> as then I will no trace of it. i don't understand that semantically. i see your point. my argument for a default-volume is still, that it is more accessible...

we can also define the default in the sample `docker-compose.yml`. some clarification about the directories that should be volume'd to preserve an instance with its customizations and uploaded files in...

fyi, there are Docker-features somewhere on the road (1.7 is the current milestone for that) that would allow us to 'hardcode' a good default: - https://github.com/docker/docker/issues/3465 - https://github.com/docker/docker/pull/8177

actually, referring to [this documentation](https://docs.docker.com/reference/builder/#volume) the behaviour you describe (the empty `…/all/modules`-folder in your `Dockerfile`), which i can reproduce, would rather be a bug: > The docker run command initializes...

and somewhere else i read, that the `VOLUME`-directive wouldn't be inherited by sub-sub-images/-containers. so no sub-image would be forced to use any volume. while there is a proper default for...