The way to do this, will depend of your base image. Of course, to be able to use Xdebug you must install it on your Docker container. You can clone this repository as base to follow this gude as it contains a basic Symfony Flex application with all the Docker stuff explained in this article included.I assume you have a basic Knowledge of Docker, PHP and XDebug.Some things might work a little different in other Operating Systems. This was tested on an Ubuntu 18.04 machine with PHPStorm 2018.1.4 and latest versions of Docker and Docker Compose.It will guide you to step by step through the process of installing and configuring Xdebug and PHPStorm with a Dockerized Symfony 4 application.
Thats why I decided to write this article. I couldn’t find a single guide that have all the steps from start to finish. And in case of getting Xdebug to work, its not an easy task. Also some things that were very easy in a normal development environment running locally, like debugging your application from your IDE, now requires some extra configuration. There is an extra complexity of maintaining all the Docker stuff. Docker make it such much easier, faster and consistent.īut everything comes with a price. I still remember being like the first 3 days when I joined my current company, configuring the project and all the related libraries and tools. These advantages are even greater when working on a team or enterprise context. Thanks to it, it is really easy for everyone to run a complex application with a single command, without having to worry about the inner details like dependencies. On some older versions of Composer, the default cache director can be located at ~/.Docker has changed dramatically the way we develop applications. The default values defined in docker-compose.yml match the default values for the composer and yarn directories:Ĭomposer cache directory: ~/.cache/composer Configuring you package manager ¶Ĭomposer and Yarn caches are shared between the host and the containers to accelerate the installation of Akeneo PIM dependencies. You won’t face this problem on Mac OS and Windows hosts, as those systems use a VM between the host and Docker, which already operates with appropriate UID/GID. Otherwise you’ll end up with a non-working PIM. So, on Linux hosts, it is mandatory that the user of your host machine has 1000:1000 as UID and GID too. These containers all have a default user with 1000:1000 as UID:GID.
The PIM root is available as /srv/pim inside the containers. The PIM is shared with the containers as a volume. Docker-compose 1.24+: docker-compose installation
0 kommentar(er)
