guides: Add Docker+Laravel example

Signed-off-by: David Karlsson <[email protected]>

Author: rw4lll

content/guides/frameworks/laravel/_index.md

@@ -0,0 +1,46 @@
+---
+title: Develop and Deploy Laravel applications with Docker Compose
+linkTitle: Laravel applications with Docker Compose
+summary: Learn how to efficiently set up Laravel development and production environments using Docker Compose.
+description: A guide on using Docker Compose to manage Laravel applications for development and production, covering container configurations and service management.
+tags: [frameworks]
+languages: [php]
+aliases:
+  - /frameworks/laravel/
+params:
+  time: 30 minutes
+  resource_links:
+    - title: Laravel
+      url: https://laravel.com/
+    - title: Docker Compose
+      url: /compose/
+    - title: Use Compose in production
+      url: /compose/how-tos/production/
+    - title: Repository with examples
+      url: https://github.com/dockersamples/laravel-docker-examples
+---
+
+Laravel is a popular PHP framework that allows developers to build web applications quickly and effectively. Docker Compose simplifies the management of development and production environments by defining essential services, like PHP, a web server, and a database, in a single YAML file. This guide provides a streamlined approach to setting up a robust Laravel environment using Docker Compose, focusing on simplicity and efficiency.
+
+> **Acknowledgment**
+>
+> Docker would like to thank [Sergei Shitikov](https://github.com/rw4lll) for
+> his contribution to this guide.
+
+The demonstrated examples can be found in [this GitHub repository](https://github.com/dockersamples/laravel-docker-examples). Docker Compose offers a straightforward approach to connecting multiple containers for Laravel, though similar setups can also be achieved using tools like Docker Swarm, Kubernetes, or individual Docker containers.
+
+This guide is intended for educational purposes, helping developers adapt and optimize configurations for their specific use cases. Additionally, there are existing tools that support Laravel in containers:
+
+- [Laravel Sail](https://laravel.com/docs/11.x/sail): An official package for easily starting Laravel in Docker.
+- [Laradock](https://github.com/laradock/laradock): A community project that helps run Laravel applications in Docker.
+
+## What you’ll learn
+
+- How to use Docker Compose to set up a Laravel development and production environment.
+- Defining services that make Laravel development easier, including PHP-FPM, Nginx, and database containers.
+- Best practices for managing Laravel environments using containerization.
+
+## Who’s this for?
+
+- Developers who work with Laravel and want to streamline environment management.
+- DevOps engineers seeking efficient ways to manage and deploy Laravel applications.

content/guides/frameworks/laravel/common-questions.md

@@ -0,0 +1,37 @@
+---
+title: Common Questions on Using Laravel with Docker
+description: Find answers to common questions about setting up and managing Laravel environments with Docker Compose, including troubleshooting and best practices.
+weight: 40
+---
+
+<!-- vale Docker.HeadingLength = NO -->
+
+## 1. Why should I use Docker Compose for Laravel?
+
+Docker Compose is a powerful tool for managing multi-container environments, particularly in development due to its simplicity. With Docker Compose, you can define and connect all necessary services for Laravel, such as PHP, Nginx, and databases, in a single configuration (`compose.*.yaml`). This setup ensures consistency across development, testing, and production environments, streamlining onboarding and reducing discrepancies between local and server setups.
+
+While Docker Compose is a great choice for development, tools like **Docker Swarm** or **Kubernetes** offer advanced scaling and orchestration features, which may be beneficial for complex production deployments.
+
+## 2. How do I debug my Laravel application with Docker Compose?
+
+To debug your Laravel application in a Docker environment, use **Xdebug**. In the development setup, Xdebug is installed in the `php-fpm` container to enable debugging. Ensure Xdebug is enabled in your `compose.dev.yaml` file by setting the environment variable `XDEBUG_ENABLED=true` and configuring your IDE (e.g., Visual Studio Code or PHPStorm) to connect to the remote container for debugging.
+
+## 3. Can I use Docker Compose with databases other than PostgreSQL?
+
+Yes, Docker Compose supports various database services for Laravel. While PostgreSQL is used in the examples, you can easily substitute **MySQL**, **MariaDB**, or even **SQLite**. Update the `compose.*.yaml` file to specify the required Docker image and adjust your `.env` file to reflect the new database configuration.
+
+## 4. How can I persist data in development and production?
+
+In both development and production, Docker volumes are used to persist data. For instance, in the `compose.*.yaml` file, the `postgres-data-*` volume stores PostgreSQL data, ensuring that data is retained even if the container restarts. You can also define named volumes for other services where data persistence is essential.
+
+## 5. What is the difference between development and production Docker configurations?
+
+In a development environment, Docker configurations include tools that streamline coding and debugging, such as Xdebug for debugging, and volume mounts to enable real-time code updates without requiring image rebuilds.
+
+In production, the configuration is optimized for performance, security, and efficiency. This setup uses multi-stage builds to keep the image lightweight and includes only essential tools, packages, and libraries.
+
+It’s recommended to use `alpine`-based images in production for smaller image sizes, enhancing deployment speed and security.
+
+Additionally, consider using [Docker Scout](/manuals/scout/_index.md) to detect and analyze vulnerabilities, especially in production environments.
+
+For additional information about using Docker Compose in production, see [this guide](/compose/how-tos/production/).