maketank/Froxlor
2
0
Fork 0
Code Pull Requests Releases Activity

Minor rewording

Browse Source 
Signed-off-by: Florian Aders <eleras@froxlor.org>
This commit is contained in:
Florian Aders
2016-01-31 12:27:00 +01:00
parent c36fb7e809
commit 435edd53f2
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -59,15 +59,15 @@ http://files.froxlor.org/releases/froxlor-latest.tar.gz [MD5](http://files.froxl
http://files.froxlor.org/gentoo/repositories.xml http://files.froxlor.org/gentoo/repositories.xml
## Let's encrypt support ## Let's Encrypt support
This version of Froxlor contains a beta - version of support for [Let's Encrypt](https://letsencrypt.org). This is (as Let's Encrypt is in itself) This version of Froxlor contains a test - version of support for [Let's Encrypt](https://letsencrypt.org). This is (as Let's Encrypt is in itself)
still a test - version and may break your system. The way it currently works is by creating a (sub-)domain with the default system - certificate, still a beta - version and may break your system. The way it currently works is by creating a (sub-)domain with the default system - certificate,
after which the Let's Encrypt cronjob orders the certificate for this (sub-)domain and inserts the certificates in the database. With the next run after which the Let's Encrypt cronjob orders the certificate for this (sub-)domain and inserts the certificates in the database. With the next run
of the default cronjob, the certificates will be updated on the disk and the webserver reloaded. of the default cronjob, the certificates will be updated on the disk and the webserver reloaded.
This has 2 known side-effects at the moment: This has 2 known side-effects at the moment:
* The ip/port combinations don't work with the Froxlor - integration of Let's Encrypt, since it needs a certificate for the very first creation * The basic ip/port combinations don't work with the Froxlor - integration of Let's Encrypt, since it needs a certificate for the very first creation
* After creating a domain, it will have the default certificate for a short time (by default 5 minutes until the cronjob runs the next time) * After creating a domain, it will have the default certificate for a short time (by default 5 minutes until the cronjob runs the next time)
It may be possible to fix these issues, but they are not a priority at the moment It may be possible to fix these issues, but they are not a priority at the moment