A customized Docker image to run Laravel apps behind a reverse proxy.
Package is not part of official Laravel environment.
This Docker image is a fork of official Laravel Sail image with some additional features inspired by approach used in dunglas/symfony-docker package.
Instead of using local PHP web server, it provides a PHP-FPM entrypoint along with Laravel specific tasks: application key generation, installing dependencies and running migrations on container start.
Latest version also includes a Supervisor configuration with two artisan queue:work processes to run jobs in background.
Image is designed to be used in Laravel 9+ applications. Installation of Laravel Sail itself is not required. On the other hand, a web server (local or container) is required to act as a reverse proxy for PHP-FPM container. An example docker-compose file can be found in this repository, featuring Caddy as reverse proxy.
Image can be pulled from Docker Hub
docker pull sauromates/laravel-fpm:latestOr included in docker-compose.yml
version: '3'
services:
php:
image: sauromates/laravel-fpm
...Please note:
Image is relying internally on the fact that application source code is mounted in /var/www/html folder inside container. In order to override this you should create your own Dockerfile based on this image along with Supervisor configuration.
The deploy is quite simple once you have configured a web server container. In most use cases you can simply clone your application on the server and run single docker-compose up -d command. In default environment, not even a build process is needed.
Only 2 things are needed to deploy production-ready containerized Laravel app with Caddy: public folder binding and Caddyfile. Example of Caddy container configuration can be found in docker-compose file under the caddy service. Example of Caddyfile is provided below.
{$SERVER_NAME}
log
route {
root * /var/www/html/public
php_fastcgi php:9000
encode zstd gzip
file_server
}
In this example {$SERVER_NAME} should be configured in your application's .env file (in most cases, it can be the same as APP_URL variable).
Also, php_fastcgi directive should contain the name of your application Docker service name and default FPM port, which is 9000.
Due to specifics of image build some issues mught occur with permissions to public folders between host machine and containers. For instance, Laravel app must give permissions to public, storage and bootstrap folders for web server user (usually www-data). Wrong permissions would end with Internal server error in production.
To fix it, make sure to give permissions to these folders for www-data user on host machine. One can achieve this with following commands.
#!bin/bash
# Give ownership to www-data user
chown -R www-data:www-data /var/www/html
# Make all files with 644 permissions and all folders with 755 permissions
find /var/www/html -type f -exec chmod 644 {} \;
find /var/www/html -type d -exec chmod 775 {} \;
# Give access to storage and bootstrap folders
chmod -R u+rwx storage bootstrap/cache
While using this image with Caddy container in local development environment an issue may arise with application not accessible via https://localhost. A workaround to this is to comment out SERVER_NAME environment variable in .env file and add environment to docker-compose.yml:
caddy:
image: caddy:2
...
environment:
SERVER_NAME: ${SERVER_NAME:-localhost, localhost:80, caddy:80}