http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15303
Mirko Tietgen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #45408|0 |1 is obsolete| | --- Comment #8 from Mirko Tietgen <[email protected]> --- Created attachment 45409 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=45409&action=edit Bug 15303 Letsencrypt option for Debian package installations Apache file for https only setups with automatic certificate generation via letsencrypt. We need a workiung web server for the letsencrypt magic, but we can't start on 443 without certs. So we start on 80, get the certs, switch to 443 and restart apache. 80 gets forwarded to https. New option koha-create --force-https - generates letsencrypt certificates - sets up a https-only website - redirects 80 to https (not yet) Test plan: - build a debian package with patch applied - checkout letsencrypt on the machine where you are testing the package git clone https://github.com/letsencrypt/letsencrypt - use apache mod_ssl sudo a2enmod ssl - make sure the machine is accessible on 80 (needed for letsencrypt) and 443 from the internet - install koha with your new package - use koha-create with the new options: sudo koha-create --create-db --force-https --letsencrypt /home/mirko/letsencrypt <instance> - wait until setup is finished, check that you got a working OPAC and staff client with certificates make sure to use https:// to open both sites Todo - use letsencrypt default path in debian when we know where that is - enable redirect from port 80 to https in apache config -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
