Hello there! 👋
We have released three minor updates for EasyEngine – 4.0.7, 4.0.8 and 4.0.9.
If your site is on CloudFlare, you don’t have to manually add TXT records in DNS anymore, while creating the site with SSL. EasyEngine will add the TXT records for you and even clean them once they’re no longer needed.
To enable CloudFlare integration, you need to provide CloudFlare account email and its API key in the EasyEngine config using the commands below.
ee config set le-mail email@example.com
ee config set cloudflare-api-key <cf-api-key>
For the time being, EasyEngine requires the Let’s Encrypt email to be the same as the Cloudflare email. Therefore, you will need to pass the Cloudflare email value to the
⚠️ Note: The site needs to be added into your CloudFlare account for this feature to work. The sites must be using CloudFlare DNS, other CloudFlare services are optional.
We’ve also upgraded our updating process to ensure that you face as little downtime as possible, while updating EasyEngine.
The main reason behind the downtime was that when you updated EasyEngine, we are required to update your running containers. Therefore, we used to stop those containers and then start new ones. In some cases, like for MySQL container, it sometime took longer to restart.
Our solution for this, before stopping the old container:
- Start a temporary container which is a replica of the old container.
- Stop the old container and start the new container.
- Once the new container is up, remove the temporary container.
This allows us to minimize the downtime and deliver near zero downtime updates.
ee site publishto
ee site share–
site sharegives a more appropriate description of the feature and its function than
site publish, we renamed the command.
- Disable TTY allocation in shell command when not needed – It was impossible to
onSSH, in environments where TTY allocation was not possible. i.e. CI/CD environments. So we disabled allocating TTY when
is passed. Hence, you can now flag run
ee shell example.com --command='<cmd>'
- Fixed the multisite login issue on
sub sites– We faced a bug where we couldn’t log in from sub sitesin MU, in cases where the sub sitewas not a subdomain of the main site
For a more detailed breakdown, have a look at our release notes on GitHub: