2. As you can see - my client uses rebar/erlang.mk and can resolve links from hex. I can't say it is 100% compatible, but it even can build package from rebar project.
To gain even better security - you can start your own build server and mention it as repository in the client's config. Server is started with one command `docker-compose up -d` - quite simple.
To gain better security - you can fork repo (that is why I use namespace/name in packages).
> 1. i would never pull a pre-built binary from a 3rd party into one of my1. You can't push any built package to the server. You can only ask server to go to github, pull the sources and build the package. Security is the same as you will clone and build github repository.
> projects. lol security?
> 2. that this project doesn't address rebar3/relx/hex at all means it is at
> odds with the direction the community has been pushing toward for several
> years now, and makes it relatively useless
But the main reason of using python is - it has lots of plugins and modules. For now I use only Jinja2 templating in erlang configs, but theoretically we can use any plugin available in ansible.
2018-02-12 18:49 GMT+01:00 <[hidden email]>:
Send erlang-questions mailing list submissions to
erlang-questions mailing list
|Free forum by Nabble||Edit this page|