Warden 0.10.1

Bug Fixes:

• Fixed a bug where SSH Agent forwarding would break following container restart (#307 by @ihor-sviziev)
• Fixed a issue where Xdebug 3 images would generate excessive profile data when running CLI commands in debug container (#309 by @Den4ik)

Please note that you must pull the latest php-fpm images via warden env pull to get these bug fixes relating to configuration in the pre-built images.

Enhancements:

• There is now a warden db dump command available to run mysqldump on the db container (#310 by @Den4ik)
• Bash history will now be persisted via an additional bashhistory:/bash_history volume on php-fpm containers (#304 by @Den4ik)

Warden 0.10.0

Upgrade Notes:

• Various updates to PHP images have occurred since the last major release including a transition to using Remi vs IUS for RPMs. It's highly recommended you re-pull to get the latest images and update your projects: warden env pull && warden env up
• Warden now requires mutagen 0.11.8 or later for environments leveraging sync sessions on Mac OS. Reference issue #235 for details. This is to resolve an incompatibility between earlier versions of Mutagen and Docker Desktop 2.3.0.5 and later.
• There is a new docs page on DNS resolver configuration thanks to @Skullsneeze
• The docs page on Installing Warden includes a new section titled Trusted CA Root Certificate with additional post-install information largely relevant to Linux users.
• Images for Varnish 6.4 and 6.5 are now available in addition to 6.0 LTS and 4.1 to support users who desire to remain closer to the bleeding edge.
• Redis 6 and Elasticsearch 7.11 images have recently been made available.
• When updating to Composer v2 using the new COMPOSER_VERSION=2 setting, make sure you remove hirak/prestissimo from global (if present) composer global remove hirak/prestissimo
• Warden will no longer attempt to auto-configure DNS resolution for *.test on non-Darwin systems due to a combination of security reasons, lack of per-TLD resolver configuration (as is used on Darwin/Mac OS) and the myriad permutations of resolver configuration across various Linux based distros. The dnsmasq container will still be started, but a warning will now be emitted on Linux directing users to the new docs page on DNS resolver configuration.

Bug Fixes:

• The .idea directory is no longer ignored from Mutagen sync allowing bin/magento dev:urn-catalog:generate to be generate metadata the IDE uses (issue #291)
• Installing on WSL will no longer report innocuous errors related to lack of systemd support on WSL as the install routine no longer makes calls to systemctl on Linux systems (issue #220)

Enhancements:

• Added opt-in support for Xdebug 3 (see docs for details; new environments will set PHP_XDEBUG_3=1) (#279 by @Den4ik)
• Added ability to provide persistent additional configuration to dnsmasq service (issue #214)
• Added ability to easily specify alternate nameservers for dnsmasq to use (issue #214)
• Added ability to customize bundled environment compositions by overriding them in the Warden home dir (#228 by @k4emic)
• Added ability to override sync configuration on a per-project basis or provide one on env types such as local where default one does not exist (#246 by @Den4ik)
• Updated version of Portainer from 1.24.X to 2.0.X (#245 by @MarcoFaul)
• Added support for COMPOSER_VERSION in .env to configure composer to run the newer Composer v2. At this time the default remains Composer v1 for compatibility reasons (issue #296)
• Added modman support for magento1 environment type (#290 by @norgeindian)

Warden 0.9.1

Bug Fixes:

• Fixed bug on WSL2 where Xdebug connect back host was improperly set (#213 by @iihor-sviziev)

Warden 0.9.0

Upgrade Notes:

• Removed deprecated first-class commands warden start, warden stop, warden up, warden down, and warden restart; please use warden svc <verb> to manage global services such as Traefik, Portainer, Mailhog, etc (#205 by @davidalger)

Enhancements:

• Added a new wordpress environment type pre-configured for running the Wordpress application (#206 by @jamescowie)

Warden 0.8.2

Enhancements:

• Changed all :delegated mounts to :cached mounts to preserve existing behavior of mounts when new behavior in Docker Desktop Edge 2.3.2.0 is promoted to stable channel (#204 by @davidalger)

Warden 0.8.1

Enhancements:

• Updated default version of PHP for new magento2 environments to PHP 7.4
• Updated default version of Elasticsearch for new magento2 environments to Elasticsearch 7.6
• Updated default version of Elasticsearch where unspecified in project's .env file to Elasticsearch 7.8
• Dropped Elasticsearch image builds for versions prior to 6.8 and versions 7.0 through 7.5

Bug Fixes:

• Fixed issue where nginx would unexpectedly exit on Linux due to incorrect default value for XDEBUG_CONNECT_BACK_HOST in base nginx configuration (issue #200)

Warden 0.8.0

Upgrade Notes:

• To ensure Traefik 2.2 version update takes effect, run warden svc up after updating.
• Pre-existing projects may need to be re-created to avoid warnings from docker-compose regarding unused named volumes.
• The BYPASS_VARNISH flag (deprecated in 0.5.0) has been removed. Use toggle WARDEN_VARNISH=0 to disable Varnish.
• Recently updated php-fpm images now include the crontabs package with crond running in the background. Be sure you have the latest images by running warden env pull in the project directory followed by warden env up to use this functionality.

Enhancements:

• Added warden vnc command to launch VNC tunnel via SSH or (when installed) launch Remmina (#116 by @lbajsarowicz)
• Updated warden env, warden svc and warden db to print help text when called without any parameters specified
• Updated volume declarations for RabbitMQ and Redis services to use named volumes (avoid use of anonymous volumes)
• Updated version of Traefik from 2.1 to 2.2
• Updated warden debug to also pass host.docker.internal into the php-debug container for the XDEBUG_REMOTE_HOST value on WSL when Microsoft is present in /proc/sys/kernel/osrelease (#196 by @LeeSaferite)

Warden 0.7.0

Upgrade Notes:

• With mailhog being changed from running on a per-project basis to running as a global service (see issue #175) you will need to ensure warden svc up has been run after updating Warden. On pre-existing projects that already had their own Mailhog container running, warden env up --remove-orphans will clean it up.

Enhancements:

• Added warden blackfire command for easily running profiles via the CLI tool (#188 by @navarr)
• Changed mailhog service to run as a single global service rather than as a per-project service (issue #175)
• Updated warden db import to strip usages of @@GLOBAL.GITD_PURGED and @@SESSION.SQL_LOG_BIN from database dumps during import process to avoid failures importing databases originating from Amazon RDS (issue #162)
• Added Mutagen sync configuration for magento1 environment type (issue #97)

Warden 0.6.0

Upgrade Notes:

• Warden now requires docker-compose 1.25.0 or later; see issue #165
• Warden now requires mutagen 0.11.4 or later for environments leveraging sync sessions on Mac OS (currently Magento 2 and Shopware 6 use Mutagen).

Enhancements:

• Added warden svc command to control global services replacing warden start, warden stop, warden up, warden down, and warden restart and offering further flexibility as this works similar to warden env in that any verb known to docker-compose may be used in orchestrating global services such as traefik, dnsmasq and portainer; for example, warden svc up does what warden up did previously.
• Updated warden env to report an error if Docker does not appear to be running.
• Updated warden env up to imply -d (--detach) to work in like manner to warden svc up (formerly warden up)
• The warden sync command now allows use of mutagen sub-commands flush and reset
• The following version defaults were updated (these defaults apply when versions remain unspecified in a project's .env file; new project .env files may differ by environment type)
  • PHP-FPM default updated from 7.3 to 7.4
  • Elasticsearch default updated from 6.8 to 7.7
  • RabbitMQ default updated from 3.7 to 3.8
  • MariaDB default updated from 10.3 to 10.4
• Updated warden env-init command to prompt user before overwriting an existing .env file in a project directory (#166 by @Lunaetic)
• Updated warden env-init command to prompt user for required arguments when missing (#170 by @Lunaetic)
• Added support for Magepack advanced JS bundling (#138 by @vbuck)
• Added a new shopware environment type including Mutagen configuration for file sync on macOS (issue #169)
• Added support for implementing custom commands in ~/.warden/commands or <project>/.warden/commands (#172 by @davidalger)
• Added new feature flag WARDEN_NGINX to enable/disable service on per-project basis. This will allow (for example) using a local env type for a static site by adding WARDEN_NGINX=1 to the project's .env file.
• Added ability to pass arguments to and override the database name db connect and db import operate on (issue #22)

Bug Fixes:

• Fixed issue where specifying -v flag would short circuit argument parsing (this flag was removed; previously was only used with warden sync list where warden sync list -l now accomplishes the same thing by passing the -l flag to mutagen to list in detail)
• Fixed bug where quoted arguments like "foo bar" would be passed into sub-route as two arguments, foo and bar (technical detail of argument parsing; no known cases where this caused an issue)
• Fixed incorrect var name in output of warden env-init for Laravel env type

Deprecated Functionality:

• The warden start command has been deprecated and will be removed in the 0.7.0 release; please use warden svc start instead.
• The warden stop command has been deprecated and will be removed in the 0.7.0 release; please use warden svc stop instead.
• The warden up command has been deprecated and will be removed in the 0.7.0 release; please use warden svc up instead.
• The warden down command has been deprecated and will be removed in the 0.7.0 release; please use warden svc down instead.
• The warden restart command has been deprecated and will be removed in the 0.7.0 release; please use warden svc restart instead.

Warden 0.5.3

Bug Fixes:

• Reverted filtering of GTID SET commands as added in 0.5.2 release to resolve db import errors (issue #162)