You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Safer backups and restores. A restore is now a transaction: it checks the free space first, stages everything next to the site, checks the restored nginx config, and rolls back config, files and database on any failure. Every archive is tested before it's uploaded, a completed backup is never deleted because a later step failed, and retention keeps exactly no-of-backups backups.
Recoverable container upgrades.ee cli update checks each recreated global service, waits for it to be ready and rolls back to the previous images when one fails. Stopped global services and disabled sites are handled instead of only recording their new image tags.
Let's Encrypt fails closed. A site whose certificate couldn't be issued, or is still waiting for manual DNS-01 validation, stays on plain HTTP instead of redirecting to a broken HTTPS.
Host logs can't fill the disk. The host's syslog and mail logs get a 2 GB size cap and hourly rotation, and EasyEngine's own logs rotate by rename instead of copying, so a rotation never needs as much free space as the log.
Updated images: postfix 3.11.7, OpenResty 1.31.8.1, nginx-proxy with ssl_reject_handshake, and PHP 8.1–8.5 with safer session defaults.
Upgrade notes
Backups now go to a per-host directory
New backups are stored under <rclone-path>/<site>/<host-id>/<backup-id>. The host id is generated on the first backup or restore and kept in the EasyEngine database; backup-host-id in config.yml overrides it.
Existing backups stay where they are and can still be listed and restored. ee site restore without --id takes this server's newest backup first, then the newest backup in the old layout (with a warning). Backups of other servers are only restored when named with --id=<host-id>/<backup-id>.
Old-layout backups are no longer pruned automatically, since they may belong to another server using the same rclone-path. Remove them by hand when you no longer need them: list them with rclone lsf --dirs-only <rclone-path>/<site>/, then rclone purge <rclone-path>/<site>/<backup-id> for the backup ids at that level (never the <host-id>/ directories).
To keep using the backups of a server this one replaces, set backup-host-id: <old host id> in this server's config.yml, or restore once with --id=<old-host-id>/<backup-id>.
Scripts that build <rclone-path>/<site>/<backup-id> paths themselves need to add the host directory. The EasyEngine Dashboard's remote_path already includes it.
Older EasyEngine versions can't restore a WordPress backup made by this version.
What a restore does now
A restore replaces all of the site's app/ directory (for WordPress, everything except WordPress core), so files created after the backup are removed. It needs the extracted size of the backup free next to the site, on top of the download, and refuses up front when that space isn't there.
When a restore replaces the site directory, the site's containers are restarted at the end.
A restore that was interrupted is rolled back by the next ee site restore, and ee site backup refuses to back up a half-restored site.
Database names used with backup and restore may only contain letters, digits and _ . @ % + = , : -, and can't start with -.
Backup behaviour
WordPress backups now hold all of app/ except WordPress core and tool caches, so files such as robots.txt, verification files, .user.ini and custom directories are kept.
Files that a symlink points to outside the site (for example uploads on another mount) are backed up as the link only, with a warning.
no-of-backups must be a whole number of at least 1. Any other value falls back to the default of 7 with a warning.
When the EasyEngine Dashboard success callback fails, the uploaded backup is now kept and the command fails with error 4004.
New error codes: 2013 (a required tool is still missing after the install), 3005 (an archive failed its integrity check), 4004 (the EasyEngine Dashboard success callback failed; the backup was kept), 4005 (the database dump couldn't be moved into the backup).
Host log rotation and the rsyslog package
On Linux, the update adds maxsize 2G (and a dateformat that allows several rotations a day) to each stanza of /etc/logrotate.d/rsyslog that has no size limit yet, and makes logrotate run hourly (a logrotate.timer drop-in, or /etc/cron.hourly/ee-logrotate on hosts without the timer). The original rule is saved in /opt/easyengine/.backup/logrotate/. This happens once: if you change or remove the cap later, updates don't put it back.
/etc/logrotate.d/rsyslog is a dpkg conffile. Because EasyEngine edits it, a later rsyslog package update that changes this file is held back by unattended-upgrades ("conffile prompt … needs to be upgraded manually"), and apt upgrade asks which version to keep. Upgrade rsyslog by hand (sudo apt-get install --only-upgrade rsyslog) and either keep the installed version or take the package's version and add maxsize 2G back to each stanza.
EasyEngine's own log rules (ee_cli, ee_sites, ee_nginx_proxy) get maxsize 1G and now rotate by renaming the log and having nginx and php-fpm reopen it, instead of copytruncate.
Containers are updated
The update moves the global services and enabled sites to the new images listed below. Each recreated global service is checked, and the update rolls back to the previous images if one doesn't come up.
Stopped global services keep their old image until you enable them, and ee service enable then recreates the service on the new image. Missing global services are recreated.
Disabled sites get updated compose files and pick up the new images when you enable them.
Sites whose Let's Encrypt certificate is still pending stay on HTTP during the image migration.
PHP requirement checks
ee now checks the PHP extensions and functions it needs before a command runs, and names the disabled functions and the ini files that disable them (for example on HestiaCP servers). A failed requirement check now exits with status 1. Site commands keep working when pcntl_* or shell_exec are disabled.
All other images (mariadb, mailhog, PHP 5.6–8.0 and easyengine/php) are unchanged.
Known issues
ee cli self-uninstall leaves the edited /etc/logrotate.d/rsyslog, the hourly logrotate drop-in or cron job, and EasyEngine's own logrotate rules in place, and removes /opt/easyengine/.backup/logrotate/ with the copy of the original rsyslog rule. Copy that backup elsewhere first if you plan to uninstall.
Images are still built for amd64 only; arm64 support is planned for the next release.
After merge
Merge develop into master and push the signed v4.14.0 tag once the pre-release checks pass. CI then builds the phar, publishes it to easyengine-builds and creates the draft release, which gets reviewed before publishing.
Summary by CodeRabbit
Chores
Updated EasyEngine to version 4.14.0.
Refreshed versions of several bundled commands and site types.
Updated runtime images for web servers, PHP, Redis, mail, scheduled tasks, and monitoring. Other bundled images remain unchanged. These updates keep the release’s included components and runtime environments aligned with their updated versions.
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: 057b72a7-6284-4865-bb80-bf95b6e759d3
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
Trigger review
No actionable comments were generated in the recent review.
Walkthrough
Changes: Release Metadata
Layer / File(s)
Summary
Release version updates VERSION, composer.json, img-versions.json
The release marker changes to 4.14.0. Six EasyEngine package constraints and the listed cron, nginx, PHP, postfix, Redis, and New Relic image versions are updated.
Change: Other
Merge Risk: Minimal · up to dabae
Merge Risk:⚪ Minimal · up to dabae
This release bump updates the version marker, selected package constraints and image tags to 4.14.0. No concrete merge-blocking risk was found; the normal release checks still apply.
Architecture risk: Low · up to 5ca48
The change affects 3 systems.
Changed systems:composer.json, img-versions.json, VERSION
Architecture concerns
No architecture-level concerns identified.
Review details
Systems and components
observed — composer.json (service) was modified; 1 changed file maps to changed impact.
observed — img-versions.json (service) was modified; 1 changed file maps to changed impact.
observed — VERSION (service) was modified; 1 changed file maps to changed impact.
Before / after behavior
observed — Modified behavior in VERSION: The version value changed from 4.13.3 to 4.14.0.
observed — Modified behavior in composer.json: Updated the version constraints for admin-tools-command, dash-command, service-command, site-command, site-type-php, and site-type-wp; the other listed package constraints are unchanged.
observed — Modified behavior in img-versions.json: The image version map updates cron from v4.11.0 to v4.14.0, nginx-proxy from v4.13.0 to v4.14.0, and nginx from v4.11.0 to v4.14.0. PHP 8.1 advances from v4.13.0 to v4.14.0; PHP 8.2–8.5 advance from v4.13.3 to v4.14.0. postfix, redis, and newrelic-daemon advance from v4.13.1 to v4.14.0. The remaining image versions in this range are unchanged.
Finishing Touches
Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: 7f78ad97-9cb4-44e0-ac80-072557d903a3
Commits
Reviewing files that changed from the base of the PR and between 1a64b58 and 5ca484f.
Files ignored due to path filters: 1
composer.lock is excluded by !**/*.lock
Files selected for processing: 3
VERSION
composer.json
img-versions.json
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
site-command v3.9.0 was re-created to include EasyEngine/site-command#528, which keeps the session-sid migration's saved php.ini out of the backup staging dir.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v4.14.0.VERSIONfrom4.13.3to4.14.0.composer.json+composer.lock; only these six packages andcontent-hashchange in the lock):easyengine/site-commandv3.8.2→v3.9.0: fix(templates): drop deprecated session ID ini settings from the PHP 8.4 and 8.5 configs site-command#519, fix(restore): keep session upload progress off after restoring an older backup site-command#520, fix(ssl): keep failed and pending Let's Encrypt sites on HTTP, wait for DNS-01 propagation and keep the www redirect site-command#521, fix(site): stop following symlinks from a site's php config volume in restore, update --php and migrations site-command#522, fix(site): keep site commands working when pcntl or shell_exec is disabled site-command#523, chore(backup): rename EasyDash to EasyEngine Dashboard in messages and docs site-command#525, fix(backup): make the EasyEngine Dashboard backup callback flow consistent site-command#481, fix(backup): verify DB dump and archive integrity to prevent silent corrupt backups site-command#483, fix(backup): make backup and restore safe against data loss site-command#527 (plus the Behat suite test(site-command): add a Behat suite and CI workflow site-command#518 and CI-only ci: ignore the blocked symfony/yaml and guzzle versions in composer update site-command#524, ci(behat): ignore the symfony/config and symfony/serializer advisories site-command#526)easyengine/site-type-wpv1.12.2→v1.13.0: fix(ssl): keep the WordPress URLs on http while the site is served over HTTP site-type-wp#247, fix(migrations): read and write custom.ini through checked handles in the upload progress migration site-type-wp#248 (minor: Bug fix for #173 and #181 #248 uses the config-volume helpers added in site-command v3.9.0)easyengine/site-type-phpv1.12.2→v1.13.0: fix(migrations): read and write custom.ini through checked handles in the upload progress migration site-type-php#121 (minor, same reason)easyengine/service-commandv1.6.2→v1.6.3: fix(service): recreate a stopped global service from the compose file on enable service-command#84easyengine/admin-tools-commandv1.1.2→v1.1.3: fix(admin-tools): let phpRedisAdmin 1.27.0 serve behind the admin-tools auth admin-tools-command#56easyengine/dash-commandv1.0.1→v1.0.2: chore(dash): rename EasyDash to EasyEngine Dashboard dash-command#3 (v1.0.2is onmainand keeps feat(dash-command): add EasyEngine version to server data dash-command#1 fromv1.0.1)EasyEngine/dockerfiles v4.14.0(every bumped tag checked on Docker Hub):easyengine/php8.1v4.13.0→v4.14.0:session.upload_progress.enabledOff (fix(php): turn off session upload progress by default dockerfiles#374)easyengine/php8.2,php8.3v4.13.3→v4.14.0: same (fix(php): turn off session upload progress by default dockerfiles#374)easyengine/php8.4,php8.5v4.13.3→v4.14.0: deprecatedsession.sid_*settings dropped (fix(php): drop deprecated session ID ini settings from 8.4 and 8.5 dockerfiles#372) and upload progress Off (fix(php): turn off session upload progress by default dockerfiles#374)easyengine/postfixv4.13.1→v4.14.0: postfix 3.11.7 and/etc/aliases(fix(postfix): update postfix to 3.11.7 and ship /etc/aliases dockerfiles#368)easyengine/nginx-proxyv4.13.0→v4.14.0: Debian updates (fix(nginx-proxy): apply pending Debian updates at build time dockerfiles#369) andssl_reject_handshakefor hosts without a certificate (feat(nginx-proxy): Implement ssl_reject_handshake for missing certificates dockerfiles#300)easyengine/nginxv4.11.0→v4.14.0: OpenResty 1.31.8.1 (chore(deps): bump openresty/openresty from 1.31.1.1-bookworm to 1.31.8.1-bookworm in /nginx dockerfiles#377)easyengine/cronv4.11.0→v4.14.0: Alpine updates (fix(cron): apply pending Alpine updates at build time dockerfiles#370)easyengine/newrelic-daemonv4.13.1→v4.14.0: Alpine 3.24.3 (chore(deps): bump alpine from 3.24.2 to 3.24.3 in /newrelic-daemon dockerfiles#371)easyengine/redisv4.13.1→v4.14.0: base image refreshdevelop: fix(migration): make container upgrades recoverable and stop needless pulls and compose downloads #1953, fix(migration): upgrade or keep stopped global services and disabled sites instead of only recording their new tags #1954, fix(migration): keep a site whose Let's Encrypt certificate is pending on HTTP #1955, fix(cli): check the PHP extensions and functions ee needs before a command runs #1957, fix(logrotate): cap host syslog and mail.log growth #1958, fix(logrotate): rotate by rename and reopen instead of copytruncate #1960 (plus the Behat suite test(easyengine): add a Behat suite and CI workflow #1950 and CI-only ci: ignore the blocked symfony/yaml and guzzle versions in composer update #1959, ci(behat): ignore the symfony/config and symfony/serializer advisories #1961).Release notes (draft)
Highlights
no-of-backupsbackups.ee cli updatechecks each recreated global service, waits for it to be ready and rolls back to the previous images when one fails. Stopped global services and disabled sites are handled instead of only recording their new image tags.ssl_reject_handshake, and PHP 8.1–8.5 with safer session defaults.Upgrade notes
Backups now go to a per-host directory
New backups are stored under
<rclone-path>/<site>/<host-id>/<backup-id>. The host id is generated on the first backup or restore and kept in the EasyEngine database;backup-host-idinconfig.ymloverrides it.ee site restorewithout--idtakes this server's newest backup first, then the newest backup in the old layout (with a warning). Backups of other servers are only restored when named with--id=<host-id>/<backup-id>.rclone-path. Remove them by hand when you no longer need them: list them withrclone lsf --dirs-only <rclone-path>/<site>/, thenrclone purge <rclone-path>/<site>/<backup-id>for the backup ids at that level (never the<host-id>/directories).backup-host-id: <old host id>in this server'sconfig.yml, or restore once with--id=<old-host-id>/<backup-id>.<rclone-path>/<site>/<backup-id>paths themselves need to add the host directory. The EasyEngine Dashboard'sremote_pathalready includes it.What a restore does now
app/directory (for WordPress, everything except WordPress core), so files created after the backup are removed. It needs the extracted size of the backup free next to the site, on top of the download, and refuses up front when that space isn't there.ee site restore, andee site backuprefuses to back up a half-restored site._ . @ % + = , : -, and can't start with-.Backup behaviour
app/except WordPress core and tool caches, so files such asrobots.txt, verification files,.user.iniand custom directories are kept.no-of-backupsmust be a whole number of at least 1. Any other value falls back to the default of 7 with a warning.Host log rotation and the rsyslog package
On Linux, the update adds
maxsize 2G(and adateformatthat allows several rotations a day) to each stanza of/etc/logrotate.d/rsyslogthat has no size limit yet, and makes logrotate run hourly (alogrotate.timerdrop-in, or/etc/cron.hourly/ee-logrotateon hosts without the timer). The original rule is saved in/opt/easyengine/.backup/logrotate/. This happens once: if you change or remove the cap later, updates don't put it back./etc/logrotate.d/rsyslogis a dpkg conffile. Because EasyEngine edits it, a later rsyslog package update that changes this file is held back by unattended-upgrades ("conffile prompt … needs to be upgraded manually"), andapt upgradeasks which version to keep. Upgrade rsyslog by hand (sudo apt-get install --only-upgrade rsyslog) and either keep the installed version or take the package's version and addmaxsize 2Gback to each stanza.EasyEngine's own log rules (
ee_cli,ee_sites,ee_nginx_proxy) getmaxsize 1Gand now rotate by renaming the log and having nginx and php-fpm reopen it, instead ofcopytruncate.Containers are updated
ee service enablethen recreates the service on the new image. Missing global services are recreated.PHP requirement checks
eenow checks the PHP extensions and functions it needs before a command runs, and names the disabled functions and the ini files that disable them (for example on HestiaCP servers). A failed requirement check now exits with status 1. Site commands keep working whenpcntl_*orshell_execare disabled.Fixes and improvements
ee site update <site> --ssl=lehint. Cloudflare DNS-01 waits for the zone's authoritative nameservers (up to 120 s) instead of a fixed 10 s, a manual DNS-01 site stays on HTTP untilee site ssl-verify, and WordPress URLs follow the scheme the site is actually served over.7z t, database credentials passed through option files instead of the command line, the database dump kept out of the webroot, missing tools installed without prompts, unique backup ids, and a consistent EasyEngine Dashboard callback flow (at most one final callback, the global backup lock released before the callback retries).session.sid_*settings, andsession.upload_progress.enabledstays Off on PHP 8.1–8.5 in the images, inee site update --phpand after restoring an older backup.ee site update --phppulls the new image first and rolls back on failure.pcntl_*orshell_exec./ee-admin/pra/works again with phpRedisAdmin 1.27.0 behind the admin-tools authentication (it returned 403).Docker image updates
ssl_reject_handshake, EasyEngine/dockerfiles#300)/etc/aliases(EasyEngine/dockerfiles#368)session.upload_progress.enabledOff (EasyEngine/dockerfiles#374)session.upload_progress.enabledOff (EasyEngine/dockerfiles#374)session.upload_progress.enabledOff (EasyEngine/dockerfiles#374)session.sid_*settings dropped, upload progress Off (EasyEngine/dockerfiles#372, #374)session.sid_*settings dropped, upload progress Off (EasyEngine/dockerfiles#372, #374)All other images (mariadb, mailhog, PHP 5.6–8.0 and
easyengine/php) are unchanged.Known issues
ee cli self-uninstallleaves the edited/etc/logrotate.d/rsyslog, the hourly logrotate drop-in or cron job, and EasyEngine's own logrotate rules in place, and removes/opt/easyengine/.backup/logrotate/with the copy of the original rsyslog rule. Copy that backup elsewhere first if you plan to uninstall.After merge
developintomasterand push the signedv4.14.0tag once the pre-release checks pass. CI then builds the phar, publishes it to easyengine-builds and creates the draft release, which gets reviewed before publishing.Summary by CodeRabbit