Requesting support for hosting_https for Let's Encrypt

[pulsating-brain]

What's the situation about getting hosting_https and LE working out of the box?

I'm having great trouble getting it working on top of this container

[helmo]

Do you have your containers accessible to the open internet? As that would be a requirement for LE's validation to work.

Therefore it won't work for most local dev containers.

The target is to make hosting_https part of the distribution so then it should become easier.

Any specific 'Trouble'?

Things to follow are https://gitlab.com/aegir/hosting_https/issues/29 and https://www.drupal.org/node/2629560

[jonpugh]

What I'd like to do is to create and maintain different tags for development & production-ready containers.

So adding LetsEncrypt is a must for the production container.

[jonpugh]

@pulsating-brain I haven't tried to use it yet. Can you give any more details on what your issues were?

[PaulLebmann]

Closed the first pull request and added a pull request #41 which adds curl to all the Dockerfiles where packages are installed.
According to https://github.com/lukas2511/dehydrated/blob/master/README.md curl is a dependency of dehydrated which is used to create the let's encrypt certificates.

[PaulLebmann]

Thanks @jonpugh for adding curl to the images in the latest commit 32a66c3

I haven't tried them yet because I haven't had the time to figure out how to upgrade my hostmaster - container, but installing curl manually in the container enabled me to use LE without any issues for the last 9 months.
Nonetheless I therefore think that this issue can be closed.