<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 25 Oct 2017, at 16.27, Benoit Chesneau <<a href="mailto:bchesneau@gmail.com" class="">bchesneau@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: SourceCodeProForPowerline-Regular; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class=""><span class="Apple-converted-space"> </span>It seems lot of people are using ets to share a config generally. Maybe becauseit feels a little hackish ?</span></div></blockquote></div><div class=""><br class=""></div><div class="">The usage of code-as-a-config is “valid” approach. I’ve used that for some project. However, the reloading of config is something to consider. You need to use code:purge(…) and take all pain associated with it. The code-as-a-config works as build time config but runtime config is easy with build-in application:get_env… </div><div class=""> </div><div class=""><br class=""></div>- Dmitry<br class=""><div class=""><br class=""></div></div></body></html>