instead of having to remember the per-project ports for individual exposed services. I also have a local Nginx setup for proxying requests to various projects so that I can use, etc.

a Node service for Node-related stuff (Yarn dependencies and the front-end build process)īoth the web and php services run a similar Docker image in terms of PHP - with the difference being that web also includes Apache through which the web application is served.

a queue worker service (based on the same Docker image as the php service) for running artisan queue:work.The HOST_UID and HOST_GID are configured to be used by Apache in the web image and PHP in the php image so as not to mess up file permissions and ownership on the host machine.įor those curious, I also have the following services as a starting point for most Laravel projects: It's a Laravel app with a docker-compose.yml file in the project root, which looks a bit like this (documentation, unrelated services, and unrelated configuration settings removed for readability): version: '3' 'Running in Docker' is not very specific, so I'll start by explaining my project setup. I spent a couple of hours getting everything to work nicely, and encountered a weird (but in hindsight, sensible) issue. Most of the online guides I've found while hoping for a quick copy and paste configuration didn't end up working, and were in fact aimed at Xdebug 2 - whereas the new Xdebug 3 version changed some of the configuration setting keys. I was also recently starting work on a new Laravel project and decided to setup Xdebug so I could, well, debug. I hoped this would've happened more often, but oh well.Īfter many years of Sublime Text usage, I recently switched to VS Code, as the Sublime Text ecosystem for PHP development seems to be somewhat less active lately, based on my personal experience. So here's my second annual (as in once-per-year) blog post.

Download xdebug docker compose