Docker Compose PHP Composer Example

composer.json

{
    "require": {
        "mfacenet/hello-world": "v1.*"
    }
}

docker-compose.yml

app:
  restart: 'yes'
  image: php:7
  command: php -S 0.0.0.0:8000 /app/index.php
  ports:
    - "8000:8000"
  volumes:
    - .:/app

composer:
  restart: 'no'
  image: composer/composer:php7
  command: install
  volumes:
    - .:/app

index.php

<?php
require 'vendor/autoload.php';
use HelloWorld\SayHello;
echo SayHello::world();

@blachawk, command: php -S 0.0.0.0:8000 /app/index.php means use php inside the app container to start a web server running at port 8000 that executes /app/index.php. The very next line reads like this: expose port 8000 from the host machine, to port 8000 where the web server is running in the container. So that you can navigate to http://localhost:8000 in your browser and see what /app/index.php shows or does.

Hi guys,

Thanks for the gist

Can you advice how it's better to use composer container when you application need to run composer inside it's own container?
For example, if you use symfony/phpunit-bridge to run tests, it try to install required packages.

Restart policy of 'yes' is not valid (at least now) docker restart policies.
Also, I had to use docker-compose up to install the container.

And...it appears that the remote repository no longer exists.

[tyler.christian@ThisOne my-dir]$ git clone [email protected]:mfacenet/hello-world.git
Cloning into 'hello-world'...
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Thanks!

It just works (TM)

Thanks, worked for me!

@andyshinn How does it work with PHP 7.2?

Is there some error with PHP 7.2? I don't use PHP daily so I am not sure what the difference might be.

Perfect! thanks for share!