Skip to content

LaraEnv 0.4.16 — Deploy fixes: php-intl & nginx vhost

Choose a tag to compare

View all tags
@thayronarrais thayronarrais released this 09 Jun 22:24
v0.4.16
c20d020

What's fixed

Two bugs that broke cloud deploys to fresh Ubuntu/Debian hosts:

  • composer install failed with Class "Normalizer" not found. The PHP package list installed during apply was missing php<ver>-intl. Without ext-intl, Symfony String (used by Composer) fatals on startup. Apply now installs php<ver>-intl alongside the other extensions.
  • nginx -t failed with invalid value "http_502". The generated vhost listed http_502 in fastcgi_next_upstream. Unlike proxy_next_upstream, the FastCGI variant does not accept http_502/http_504 (those are gateway errors nginx emits itself, not FastCGI backend responses). The directive now uses http_500 http_503 only.

If you already have a host that failed mid-deploy, you can unblock it manually:

sudo apt install php8.4-intl && sudo systemctl restart php8.4-fpm
sudo sed -i 's/http_500 http_502 http_503/http_500 http_503/' /etc/nginx/sites-enabled/*.conf
sudo nginx -t && sudo systemctl reload nginx

Then re-run the deploy — both steps are idempotent and will overwrite cleanly.

Install

  • Download LaraEnv-0.4.16.msi and double-click.
  • SHA-256 in LaraEnv-0.4.16.msi.sha256.
  • Auto-update from prior versions picks this up automatically.

Compatibility

  • Windows 10+ (x64) for the desktop app.
  • Cloud deploy targets: Ubuntu/Debian (apt-based). No changes for Windows-local stacks.
  • No config or data migrations. Drop-in replacement for 0.4.15.
Assets 4
Loading