Hi Cord, On Fri, 2016-05-13 at 20:16 +0200, Cord Beermann wrote: > Package: letsencrypt.sh > Version: 0.1.0-2 > Followup-For: Bug #822493 > > Hello, > > I'd also prefer some more information how this package works. >
The still missing README.Debian is to blame on me. I'll sit down tomorrow and finally write an initial draft. > The file could also contain information how to migrate from letsencrypt (the > python-based package) to letsencrypt.sh, which is the problem i'm > looking into now. Upstream provides some information on this topic [1]. It might be worth to integrate it somehow in letsencrypt.sh. [1] https://github.com/lukas2511/letsencrypt.sh/wiki/Import-from-official-letsencrypt-client > It should contain information how the conf.d directory has to be used (as far > as i see files have to be *.sh?) and what format they should have. Yes, this is the main reason we want to have a README.Debian. I'll post a link to the draft as soon it is in our packaging repository. > PS: It would also be nice if you add a cronjob to the package for refreshing > the configured certificates. Of course, we have this in mind, too. But it will take some time to get this in place. Feel free to open a separate bug for this in BTS. Greetings Daniel
signature.asc
Description: This is a digitally signed message part
