feat(provider): support for the HTTP-01 challenge

[tgragnato]

closes #18

The functionality is designed to activate by setting "webroot" in the provider's configuration. It is the responsibility of system administrators to route HTTP traffic for the prefix /.well-known/acme-challenge/ to Inca.

TODO: There are no unit tests for the providers, and this is partially correct as we do not want to rewrite tests that cover the features provided by the library we are using (lego). However, it would be very helpful to start introducing tests for the glue code.

For now, the introduced functionality is trivial, and it seems possible to safely introduce it without implementing unit testing beforehand for this portion of the code.

NB: Static serving is heavily dependent on the WORKDIR /tmp Docker directive; everything breaks down in different environments.

[JellyBellyDev]

Maybe we should add a little bit of documentation on this feat?

[tgragnato]

Maybe we should add a little bit of documentation on this feat?

+1. A complete documentation is missing for basically everything regarding operations and the configuration yaml (not just this feature).

We could start documenting this and expand/recover a description of everything that's missing, starting from a basic skeleton.

What could be a good place for the docs?

[JellyBellyDev]

+1. A complete documentation is missing for basically everything regarding operations and the configuration yaml (not just this feature).

We could start documenting this and expand/recover a description of everything that's missing, starting from a basic skeleton.

Ok no problem. I suggest to do this in new PR! ;)

What could be a good place for the docs?

One dir documentation at the root of repo with inside all file md and in the file readme the special toc for docs?

[JellyBellyDev]

LGTM 👍

[tgragnato]

+1. A complete documentation is missing for basically everything regarding operations and the configuration yaml (not just this feature).
We could start documenting this and expand/recover a description of everything that's missing, starting from a basic skeleton.

Ok no problem. I suggest to do this in new PR! ;)

What could be a good place for the docs?

One dir documentation at the root of repo with inside all file md and in the file readme the special toc for docs?

#31