[Letsencrypt-devel] Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

[Mattia Rizzolo]

Control: retitle -1 ITP: letsencrypt.sh -- ACME client implemented in Bash

On Sun, Mar 27, 2016 at 01:01:18PM +0200, Daniel Beyer wrote:
> On Sat, 2016-03-26 at 21:07 +0000, Mattia Rizzolo wrote:
> > On Thu, Jan 21, 2016 at 08:10:13AM +0100, Daniel Beyer wrote:
> > > * Package name    : letsencrypt-sh
> > 
> > Is there a good reason not to call this package 'letsencrypt.sh', with a
> > dot, as the official name?
> 
> No, there is no good reason for it. I wrongly thought a dot in a package
> name is not permitted. Let's name it letsencrypt.sh.

Cool, let's change it ;) (I retitled the ITP here)

> > Anyway, this email was to ask how it's going with this.
> 
> Since I needed it, I made some initial packaging [1] on GitHub, which
> fit my needs right know. It of course need some more work to get it
> ready for Debian (e.g. it needs to be rebased against upstream's v0.1.0
> and the repo should be moved to anonscm.d.o).

I'd be very happy to do some work and have you review it and see if it
fits your needs and likings.

Two things I'd do include using an apache2 configuration snippet (to go
in /etc/apache2/conf.available) instead of a fake virtual host in
/etc/apache2/sites.available.

Another is to install the full config snippet provided by upstream in
/usr/share/letsencrypt.sh/examples and install our version in /etc/ from
a static copy kept in debian/ instead of patching upstream's config.sh.

> > It should be a
> > fairly simple package, and I'm quite interested in it (can also sponsor
> > it or help to comaintain it, as you like, if you need it!).
> 
> I might have overcomplicated things a bit with the current packaging
> approach (e.g. providing apache configuration). You might want to take a
> look yourself and share your thoughts.

I like that you're providing a easy snippet of conf to easily set up
apache to do

> If you're up for it, I gratefully would like to accept your offer to
> co-maintain this package. Additionally it might be worth to ask having
> it under the umbrella of Debian Let's Encrypt [2].

Yes, that's a great idea.  I'm CCing letsencrypt-devel.  I asked
hlieberman via IRC if this would be ok for him, but he hasn't replied
yet.
If this is Ok for the letsencrypt team, would you be ok to add myself
(user: mattia) and Daniel Beyer (that I guess is dabe-guest on alioth)
to the team?

> Let me know if you think we can base our work on what I've done so far,
> or if we instead should make a fresh start.

If think your work is great :)

If you are ok, I'd start working on a clone of this and see what you
think of it; it really won't need much!

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/letsencrypt-devel/attachments/20160327/0c11cbc2/attachment.sig>