Passing additional configuration

[iby]

Me again. I've been looking into this a bit more and think it would be useful to have two more options:

1. Passing ssl keys – some clients expect a secure connection and don't work with plain http, like Transmit. It would be good to have an ssl folder with key.pem, cert.pem and cacert.pem and checking them during the build if they contain only key and certificate, or CA certificate as well, or nothing at all, and updating the config accordingly.
2. Passing the cs_root_host parameter, in case we don't want to have no actual S3 access. I use s3.amazonaws.dev locally alongside with the actual s3.amazonaws.com.

I was playing with Docker and Riak CS for the past few days in attempt to learn a bit more how to use both by building own image and using your repo as a reference point. I think it's a good idea to take all config-related patching into a separate script, instead of squeezing all in the Dockerfile. I also managed to avoid copying the Riak's entire app.config by updating the existing one, it must be a better approach. If you are interested, have a look here.

Also, not sure how relevant that is, but I managed to run everything on top of a standard Ubuntu image with Supervisord to handle the processes. I've read contradicting views on phusion/baseimage and thought to try doing the leaner way. When I run a small cluster (on top of baseimage) that just sits and does nothing the CPU usages goes considerably higher. Using a lighter setup must make a difference, though that wasn't really a critical issue.

[fzhaw]

I would second the SSL option, have you worked on it a bit maybe?