New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support remote sites #3
Comments
|
It now seems to work reliably after commit 2f57cff Only a few warning remain about unlinking old files that don't exist... which could probably be fixed with an @ prefix. @omega8cc, @gboudrias please review. |
|
Hey @helmo, @gboudrias -- we have added you both to this project. Please commit any improvements you will find useful. Thanks! |
|
@helmo -- It shouldn't hardcode |
|
Good point about hardcoding /var/aegir ... now removed. Not sure what you mean by 'the feature should be optional'... this code does not interfere on a singe server setup. |
|
Thank you for the hardcoded path fix. I mean things like: This introduces requirement which is not backward compatible, so it breaks existing instances, until the This should be made optional, and not required, also because it is not needed on single-system Aegir instances. |
|
Note that BOA specific checks in this extension only modify the extension behaviour if BOA is detected, but otherwise don't affect vanilla Aegir installations (unless I have missed something?) |
|
So we should have something like this instead: |
|
I'll look into that. Might be even nicer to detect if the site is on a remote server. |
|
One extra commit added to the PR ... 140fd57 That should detect if it's on a remote server. |
|
Committed. Thanks! |
helmo commentedJun 6, 2016
Another WIP in https://github.com/helmo/hosting_le/tree/feature/remote-server
Answering the challenge works via a hook in letsencrypt.sh
It sometimes works... Setting $force_renew = TRUE is needed otherwise the good certs are overridden again with selfsigned ones.
The text was updated successfully, but these errors were encountered: