<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi all,<br>
<br>
I want to take a moment to thank Valery and everyone else working
on Enot for listening and completing the name change. A special
shutout goes to Fred and everyone else who tried to stop the
outrage about our community and one another. The wide response
snowballed pretty quickly and was less about the original post;
this has only confirmed that what we do as a community make sense
and is needed, but is also observed by others! Let's not allow
this to shadow the hard work many have done to get to where we are
today. <br>
</p>
<p>Get inspired by Sarah Allen keynote titled Language Encodes
Wisdom which sums up not only where we are, but where we should be
heading:</p>
<p><a class="moz-txt-link-freetext" href="https://www.youtube.com/watch?v=_PdcGptErsY&t=1s">https://www.youtube.com/watch?v=_PdcGptErsY&t=1s</a><br>
<br>
There is still loads to be done and we do hope many of you will
not get discouraged but instead want to fuel the future of Erlang
and inspire more people to join us. Our first goal? To welcome
ideas, opinions, and outlooks as many as there are people creating
this community free of harassment where there is reciprocal
respect. </p>
Francesco <br>
<br>
<div class="moz-cite-prefix">On 18/02/2018 21:21, Valery Tikhonov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFH5SaUxOSBLVS+-MmzquWwqWADTY61eTuo2tm3vLH-E=457Ug@mail.gmail.com">
<div dir="ltr">Hi,<br>
<br>
As promised, I have done renaming the tool. And now it is called
'Enot' [yenot] - that is raccoon in Russian. <br>
My appology for not being answering the questions before - I was
extremely busy with my personal stuff and renaming in general.
So further in letter you'll see links on updated everything :)
and answers on most questions. <br>
<br>
<br>
Here are the updated links:<br>
<a href="https://github.com/comtihon/enot"
moz-do-not-send="true">https://github.com/comtihon/enot</a> -
client<br>
<a href="https://github.com/comtihon/enot_auto_builder"
moz-do-not-send="true">https://github.com/comtihon/enot_auto_builder</a>
- server<br>
<a href="https://enot.justtech.blog/" moz-do-not-send="true">https://enot.justtech.blog/</a>
- site<br>
and updated articles:<br>
<a
href="https://justtech.blog/2018/01/07/create-erlang-service-with-enot/"
moz-do-not-send="true">https://justtech.blog/2018/01/07/create-erlang-service-with-enot/</a><br>
<a
href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy-with-enot/"
moz-do-not-send="true">https://justtech.blog/2018/02/11/erlang-service-easy-deploy-with-enot/</a><br>
<br>
The GiHhub application and it's pip package are also renamed to
enot.<br>
<br>
Now I'll try to answer your questions:<br>
First, Enot is not just another build system with new
configuration format (eh, we already have two), but It is an
easy deploy tool. You prepare your installation instructions and
every user can install your package<br>
via "enot install ..." CLI command. That's the main idea: to
have something comparable with Python's pip.<br>
Also I tried my best to design modern tool, similar to what they
have in Java and Python worlds.<br>
I took the best:<br>
* prebuilt deps [Maven, Pip]. Now all CI/docker builds will be
much faster<br>
* an easy deploy [Pip]. <br>
* multiple environment configuration [Java]. See <a
href="https://github.com/comtihon/enot/blob/master/docs/templating.md#appsrc-advanced-templates"
moz-do-not-send="true">https://github.com/comtihon/enot/blob/master/docs/templating.md#appsrc-advanced-templates</a>
for more details.<br>
* automatic name/version fill in at app.conf and relx.conf. Yes,
I think that manual handling of versions and constants is a
little bit outdated and not practical. Especially, when you have
to modify multiple files. <br>
<br>
Second, I believe Json coniguration is better for devOps, but if
you don't want to learn it: use rebar or <a
href="http://erlang.mk" moz-do-not-send="true">erlang.mk</a>
config - Enot understands them as well.<br>
<br>
Third, there were some questions about security. I've added
document here <a
href="https://github.com/comtihon/enot/blob/master/docs/packaging_and_security.md"
moz-do-not-send="true">https://github.com/comtihon/enot/blob/master/docs/packaging_and_security.md</a>
<br>
Main idea is: nobody can upload prebuilt package to EnotHub. You
can only ask Enot Build Server to fetch sources from GitHub and
build package.<br>
Also, do you really use third-party github deps in production? I
beleive not. So just fork dep you need, add it to EnotHub and
use. Enot was designed to be fork-compatible. <br>
<br>
If your company is big enough to afford private git (gitlab),
artifactory/nexus, ets. you can just run your private Enot Build
server and switch all Enot clients to it to gain even more
security.<br>
<br>
As for cryptography package checks - I also find it important
and I'll add it in a few weeks (still a little bit busy).<br>
<br>
Many thanks to people who advocate me and my appologies to
people who felt hurt. <br>
<br>
I hope nothing will stop you to use this tool at work now :).<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>