[erlang-questions] erlang in docker from scratch

[Peter Morgan]

> On 29 Mar 2016, at 00:42, Santiago Ignacio Poli <santiagopoli@REDACTED> wrote:
> 
> I thought the same thing when I was considering using Erlang in Docker, and I think it won't be possible to do hot code swapping with this approach. The only solution is to mount the code as an external volume and hot swapping it. In that case you will need to have an image for your environment and another one for your code.
> 
> 2016-03-28 16:31 GMT-03:00 Son Tran-Nguyen <son@REDACTED <mailto:son@REDACTED>>:
> Having tried Docker with Erlang, I have a question about hot code swapping. 
> Does using Docker get rid of that benefit? It seems to me that every Docker
> image will be a new release.


My workflow: in local development I sit and write code in a “make shell", until it mostly works. Turning thoughts into modules, when they get more mature, I start using make:all([load]) together with an Emakefile - quick and low ceremony. Once I have a “feature” - I commit, my CI automatically builds a release, creates and pushes a new docker image to a registry - part of the CI also pings the docker API on the integration environment to deploy and bounce the new services individually which are each hidden behind a HTTP software load balancer. The few volume mounts are for persistent data in those services, but mostly they are stateless and rely on Kafka topics to replenish their state or some other SOR.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160329/7442e1e7/attachment.htm>