mmontone/acme

Application Configuration ManagEr

acme's Issues

An idea for bindings

Bindings are implemented using acme's command line at the moment. The problem with that is that anytime a configuration variable is accessed, the whole configuration is loaded, for each variable accessed. That's too slow.

The solution to that would be to load the configuration is memory first, and then access its variables.

To do that, one option is to implement a configuration parser and variable accessor in each language (Lisp, Python, PHP, etc).

Another (and maybe less costly) option, is to implement a configuration parser and variable accessor in C language and then use each language FFI.

One more option would be to put Acme in "server mode" and use some IPC (.i.e. message passing) to load and access the configurations.

Package name clash

Hey, @mmontone :). I've started working on the https://github.com/letsencrypt/lets-encrypt-preview in October last year and since the beginning I was aiming to publish the implementation of the ACME protocol specification under Python "acme" package. Unfortunately, today, while preparing the package, I've seen your https://pypi.python.org/pypi/acme... Since the rename commit (3a68175) and PyPI upload is quite recent, I was wondering if there is any chance you could rename your project once again and transfer the PyPI package ownerhsip, please? :) Me personally, and the the Let's Encrypt Project would eternally owe you!

cc: @jdkasten, Let's Encrypt Client Lead