Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warden 0.2.0 Release #79

Merged
merged 175 commits into from
Jan 28, 2020
Merged

Warden 0.2.0 Release #79

merged 175 commits into from
Jan 28, 2020

Conversation

davidalger
Copy link
Collaborator

@davidalger davidalger commented Jan 28, 2020

Highlights

  • Traefik upgraded from v1.7 to v2.1; details in upgrade notes
  • LiveReload now supported in magento2 environment type; docs page
  • All images used by environments are now hosted on Quay.io; details in docs
  • Native support for multi-domain projects in form of wildcard routing in new Traefik v2 labeling overhaul; more info here
  • Added BYPASS_VARNISH flag for simple means of sending requests directly to Nginx if need be.
  • Updated default PHP version for magento2 environments from 7.2 to 7.3 (issue Updated default php-fpm version to 7.3 for magento2 environments #75)
  • Updated default Varnish version for magento2 environments from 4.1 to 6.0 (LTS)
  • env-init now dumps all version variables to .env file to lock them so future updates to Warden won't change versions on existing project configurations.
  • Updated minimal Mutagen version requirement to 0.10.3 and upgraded Mutagen config to YAML format.

Full Details
For complete details, please see the change log:
https://docs.warden.dev/changelog.html#version-0-2-0-2020-01-27

Many thanks to the individuals contributing to the creation of the Warden 0.2.0 release including @wcrb15, @lbajsarowicz and @molotovbliss.

…s; added livereload labels natively to php-fpm container and native multi-domain support via wildcards
# Conflicts:
#	CHANGELOG.md
#	commands/usage.help
The upstream image broke the use of TCP forwards when upgrading the base image from Alpine 3.6 to 3.10 which has AllowTcpForwarding=no by default vs yes. Options TCP_FORWARDING was added shortly therafter.
# Conflicts:
#	CHANGELOG.md
#	commands/usage.help
… below for why

On macOS a file at /etc/resolver/test is used to route only queries for *.test to the dnsmasq container. This works and only queries for .test domains are routed (and previously were logged) by the dnsmasq container. On Linux systems however, the only way to setup on name resolution for *.test domains is to configure the network manager to send all queries through the dnsmasq container. As @talesh pointed out, this poses a potential privacy issue for those linux users among us. This mitigates that by disabling the logging by default. Logging may still be enabled by going to https://dnsmasq.warden.test/ in a browser, and altering the loaded configuration.
…revent breaking changes in that base image from upsetting the tunnel
…atically re-instate the needed configuration

Resolves #59
…e undue builds of images unaffected by changes
Collapse Docker Images Into Warden Project Repository
* Moved some images around; update tags; change builds to push to quay.io

* Updated environments to utilize images from quay.io

* Added images to quay for rabbitmq and redis

* Added images for mariadb and mailhog

* Fixed incorrect tag on php-debug for magento2 env type

* Force build of all images on quay branch

* Revert "Force build of all images on quay branch"

This reverts commit a1c305a.
…the "ubuntu:bionic" layers downloaded by mariadb images
@davidalger davidalger self-assigned this Jan 28, 2020
@davidalger davidalger added this to the Warden 0.2.0 milestone Jan 28, 2020
@davidalger davidalger merged commit dcaa432 into master Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants