We have release EasyEngine v4.0.10. This marks our second release of 2019.
EasyEngine now supports adding custom SSL certificates. This means if you already have SSL certificate for a site from a third party vendor, then you can use that instead of getting a certificate from Let’s Encrypt. Here’s how you would do it.
ee site create example.com --ssl=custom --ssl-key=/root/certificate.key --ssl-crt=/root/certificate.crt
⚠️ Note: You might need to take care of certificate renewal yourself since EE can’t renew a custom SSL certificate.
EasyEngine now supports specifying custom webroot. This could especially be useful for sites which want webroot at different place. i.e. If you’re deploying the project with deployer, then your site’s code will be at
$siteroot/app/htdocs/current. In that case you can use following command:
ee site create example.com --public-dir='current'
Note that any path that you mention has to be inside
Now you can renew your SSL certs with an EE command:
ee site ssl-renew example.com
To renew all the certificates you can run:
ee site ssl-renew --all
Certificate renewal is allowed one week before the certificate will expire. You can override this limitation and force renewal with
ee site ssl-renew example.com --force
Furthermore, EasyEngine will handle cron renewal for all existing and new sites. Note that certificate of sites that have wildcard certificate or use DNS challenge will be renewed only if Cloudflare API key is present.
Swap is one of the first things we configure on a fresh server. Hence, to reduce the setup time on a fresh server, EasyEngine installer will now add a swap of 1 GB if no swap is found on server.