Glide
MediaZone uses League Glide to serve on-the-fly image transformations. A signed route handles all Glide requests.
How it works
When a media record is saved, generateUrl() builds a URL pointing at the Glide route:
The Glide server reads the original file from the configured disk, applies the requested transforms, and returns the processed image. Responses are cached by Glide on subsequent requests.
Configuration
driver
Set to gd if your server does not have ImageMagick installed. imagick is recommended for better quality and format support (including AVIF).
route_path
The URL prefix for the Glide route. Defaults to media, producing /media/glide/{id}.
route_middleware
Middleware applied to the Glide route. Defaults to ['web']. Set to [] to make images publicly accessible without session context, or add auth to protect them.
fallbacks
An array of fallback disk paths used when the primary file is not found. Useful during migrations between storage backends.
Cloud disks
For disks listed in config('media.cloud_disks'), Glide is bypassed. The original CDN/storage URL is used directly in generateUrl(). This avoids proxying large files through your application server.
Custom server factory
To customise the Glide server (e.g. add watermarks or custom presets), point glide.server at your own factory class: