Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2020-10-21 | doc: all roles | Lars Wirzenius | 1 | -0/+5 | |
2019-09-29 | Change: order of installing haproxy, running certbot | Lars Wirzenius | 1 | -6/+6 | |
For freshly installed systems so the first run doesn't fail. | |||||
2019-05-19 | Fix: how we check that haproxy_domain is set | Lars Wirzenius | 1 | -14/+11 | |
2019-02-25 | Change: use apt with list of packages, intead of looping | Lars Wirzenius | 1 | -2/+1 | |
2019-02-16 | Refactor: install daily cron job, then invoke it, instead of inline | Lars Wirzenius | 1 | -14/+14 | |
2019-01-06 | Fix: restart haproxy after Let's Encrypt certifiacte is renewed | Lars Wirzenius | 1 | -0/+1 | |
2018-11-06 | Fix: recreate haproxy.pem in cron job | Lars Wirzenius | 1 | -0/+11 | |
haproxy wants a haproxy.pem that is the catenation of letsencrypt's fullchain.pem and privkey.pem. It's created by the Ansible playbook, but if you don't run Ansible for three months, the cert will expire. Add a daily cron job that recreates haproxy.pem every day. This might be doable using a certbot haproxy plugin, but I can't be arsed to find out. Don't understand why letsencrypt doesn't just create such a file by default, or why haproxy wants such a file. | |||||
2018-08-07 | Add: check that letsencrypt_email is set | Lars Wirzenius | 1 | -2/+12 | |
2018-08-07 | Add: haproxy role | Lars Wirzenius | 4 | -0/+146 | |