[erlang-questions] Deployment rebar3
Mon May 7 17:16:43 CEST 2018
Using OS env variables would definitely speed up the process. I could have a “master” config file that is exported to the ENV and then each node would get all of the important info. Really, the changing information that just got annoying was entering the node name and IP address for the local network and the public IP addresses to listen on for certain information. This could certainly hold us over until we move into containerized systems.
On May 7, 2018, 10:51 AM -0400, Stefan Hellkvist <hellkvist@REDACTED>, wrote:
> 7 maj 2018 kl. 16:44 skrev Guilherme Andrade <g@REDACTED>:
> > > On 7 May 2018 at 15:03, Stefan Hellkvist <hellkvist@REDACTED> wrote:
> > > > What's "best" is very much depending on who you ask, but, for starters you may consider wrapping your configuration with something that allows you to override config variables with environment variables (see example below).
> > >
> > > rebar3 releases provide this out of the box:
> > >
> > > https://www.rebar3.org/docs/releases#dynamic-configuration
> It is a relx feature, yes, which works fine also in erlang.mk, but I find it sometimes inconvenient that you then HAVE to set the environment variable every time. But, agreed, it is also a good option if you start your release with a script.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions