[Letsencrypt-devel] Bug#822493: letsencrypt.sh: config file refers to nonexisting documentation
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 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. 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. Cord PS: It would also be nice if you add a cronjob to the package for refreshing the configured certificates. ___ Letsencrypt-devel mailing list Letsencrypt-devel@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
[Letsencrypt-devel] Bug#822493: Bug#822493: letsencrypt.sh: config file refers to nonexisting documentation
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 ___ Letsencrypt-devel mailing list Letsencrypt-devel@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
[Letsencrypt-devel] Bug#822493: letsencrypt.sh: config file refers to nonexisting documentation
On Fri, May 13, 2016 at 09:44:31PM +0200, Daniel Beyer wrote: > On Fri, 2016-05-13 at 20:16 +0200, Cord Beermann wrote: > > 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. Also, consider how hard can be to provide a cronjob that works for all kind of setup. I run my letsencrypt.sh under a 'letsencrypt' user, but clearly that's not everybody's setup. IMHO before providing such cronjob we should also provide a full setup, including a system user that runs letsencrypt.sh. So, feel free to open a new bug for it, but also to provide some thoughts on the matter. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ Letsencrypt-devel mailing list Letsencrypt-devel@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
[Letsencrypt-devel] Bug#824223: letsencrypt.sh: Provide more automatism for letsencrypt.sh
Package: letsencrypt.sh Version: 0.1.0-2 Severity: wishlist I continue the discussion from Bug#822493 here: Please provide a cron based automatism for refreshing certificates. It would be nice that users only need to provide the hostname(s) they want to get a certificate for in /etc/letsencrypt.sh/ and a cronjob that runs letsencrypt.sh -c takes care for refreshing it before it expires. That script would also need hooks to reload daemons that need to know about a certificate-change. Debconf could ask if automatic refresh is activated. Cord ___ Letsencrypt-devel mailing list Letsencrypt-devel@lists.alioth.debian.org https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
