[erlang-questions] Deployment rebar3

[Tristan Sloughter]

Note that you, assuming you aren't already, should use `rebar3 tar` and
not tar/zip the release directory manually.
How to deploy a release is  more of a general problem. You should be
able to use whatever your IT guys are already using for copying a
release to a node and setting up configuration -- ansible, chef, etc?
You can use either OS vars as someone pointed out or simply have one of
those configuration tools create a whole new sys.config/vm.args and
overwrite the existing files after unpacking the release.
Docker doesn't really bring you much if not also using something like
kubernetes. You still have to get the image to a node and setup per-node
configuration, not much different from doing it with the tarred release.
But kubernetes is really great for this :). I use kubernetes deployments
and stateful sets to deploy Erlang releases, with env vars for
configuring sys.config/vm.args per pod and kubernetes dns for node
discovery/clustering.
Tristan

On Mon, May 7, 2018, at 6:45 AM, asdf asdf wrote:
> Hey everyone, 
> 
> I’ve recently built a few applications that handle high volume
> message passing and all communicate with each other using Erlang’s
> ssl distribution. I’m working on deploying these to multiple servers
> - right now I am just using rebar3 release and creating a zipped tar
> of the release directory, moving it to a new box, and changing the
> some vm.args and sys.config options on the new machines. This
> doesn’t seem totally intuitive though… it take far longer than I
> feel like it should.> 
> I’ve read about Docker and Kubernetes, and those seem promising, but
> our IT guys aren’t ready to move to containers and are using static
> nodes right now.> 
> So, what is the best way to quickly distribute your erlang binaries
> and configure the enviornment? Have a quick script to do it
> automatically? Is the answer just containerize with Docker and wait a
> few months for the IT team to catch up with it? Or is there some other
> option out there?> 
> Thanks for your help!
> _________________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180507/cdffd052/attachment.htm>