Composer-docker VS Laradock

The same principle applies to any other images you may depend on, such as composer for dependency installation. Select the image tag that matches the major composer version you're using on your machine — composer:2 instead of composer:latest.

I've got a local version of PHP installed, but I really don't need it. Composer has an official docker container: https://hub.docker.com/_/composer/

I found on the docs of the composer image, in the Troubleshooting section, that composer should not be used that way. So I put it inside the Php image with COPY --from=composer /usr/bin/composer /usr/bin/composer and it worked. Thanks for the help u/effata!

I run most of the projects I develop on through a docker image. If it's a PHP project with composer dependencies, I use a composer image to install its dependencies, when I want to run it I use a php image. If the PHP image does not include the dependencies required for the project, I will look for an image within the project that is used, or build my own image serving the purpose. I like to make things easy to run and use, so that if I leave a project for a while I want it to be easy to get started again. If the project requires multiple things running, like a database, I setup docker-compose to make it easy to start a PHP container and database container alongside eachother that can communicate.

There is a hard coded case for this now in the project https://github.com/composer/docker/blob/master/1.10/docker-entrypoint.sh#L6

The /app directory is specified working directory, from composer image via https://github.com/composer/docker/blob/582c6f4e10b6b8fbf9bc1c5b02d6ec24694fe8d4/2.0/Dockerfile#L60.

Haven’t touched Laravel for years pero baka laradock might be good for your use case

This is a function of the apache configuration files. You should examine those and determine what the issue is, using the xampp gui which will let you edit the httpd.conf file, or whatever it is that xampp uses. xampp provides the default settings you need, so I highly doubt this is the issue, but there is a directive called DirectoryIndex that tells apache what files to search for when a url points to a directory. By default that is going to include index.php. So if that is not working, then there is possibly something else going on with the apache config. To figure this all out you really have to understand how the various possible configuration options work. I don't use xampp so I can't tell you with certainty what the defaults are, but directives like Directory, VirtualHost, DocumentRoot etc, can all be used and combined in different ways to create different outcomes. For example, whether or not an index even appears (in the absence of an index.php) is configurable, as is whether or not you can override settings in a .htaccess file. I'm guessing you might be running xampp under windows, and this is yet another reason why in the era of containers, it's just better to use virtualization or containerization rather than something like xampp. As it sounds like you are still in learning mode, it's not too late to turn your attention to something like docker with https://laradock.io/

It's vastly inferior to laradock and does less.

With https://laradock.io/ it should be no more than a couple of minutes. Yes, this is a development environment and not meant for production. But so is yours, just with a worse approach.

The prime example of what I'm referring to is: https://github.com/laradock/laradock

First, we will use Laravel Sail to run the application locally on our dev environment. There are unofficial Docker environments for Laravel like Laradock but Sail is the official docker dev environment for Laravel. Sail is is a wrapper on top of docker compose.

git clone https://github.com/Laradock/laradock.git