Hardcoded hosting_le code limits behavior with regards to the .well-known directory

For Nginx:

• http://cgit.drupalcode.org/provision/commit/?id=ad72ce7a0c6cca7f4af7af0d...
• http://cgit.drupalcode.org/provision/commit/?id=b0a0d9ce95541c5f52ad388e...

(or just remove the well-known block in provision/http/Provision/Config/Nginx/Inc/vhost_include.tpl.php)

It had to be hardcoded because we don't have proper frontend integration in hosting_le, so it was not possible to make the path configurable.

This can be solved via proper implementation, like hosting_certificate

Once it is configurable (either in hosting_certificate and/or in hosting_le), we can safely replace the hardcoded paths with something like d('@server_master')->http_le_path, etc.

It is not set in stone, after all, and it was a quick shot to make the first integration option working.

The path to the 'well-known' directory doesn't have to be configurable from the front-end, nor generally should it be. But it shouldn't be hard-coded into the vhost templates either. hosting_le should just implement drush_hook_provision_nginx_vhost_config() and drush_hook_provision_apache_vhost_config() to write these configs into the vhosts.

Another issue with this implementation is that the directory containing the challenges won't get sync'd to remote servers, thus limiting use of Letsencrypt to single-server deployments.

Good points! Removed. We can add this with hooks.

Moving to the correct queue.

Related commit.

We have implemented this in hosting_le, as suggested.