Sign inSign up

qoopido/php56

By qoopido

•Updated almost 10 years ago

PHP 5.6 fpm container (standalone)

Image
1

2.2K

qoopido/php56 repository overview

Like with my other containers I encourage you to follow a unified directory structure approach to keep things simple & maintainable, e.g.:

project root
  - docker-compose.yaml
  - config
    - php56
      - fpm
        - php.ini (if needed)
        - conf.d
        - ...
  - htdocs
  - data
    - php56
      - sessions
      - logs

⁠Example docker-compose.yaml

php:
  image: qoopido/php56:latest
  ports:
   - "9000:9000"
  volumes:
   - ./htdocs:/app/htdocs
   - ./config/php56:/app/config
   - ./data/php56:/app/data

⁠Or start container manually

docker run -d -P -t -i -p 9000:9000 \
	-v [local path to htdocs]:/app/htdocs \
    -v [local path to config]:/app/config \
    -v [local path to data]:/app/data \
	--name php qoopido/php56:latest

⁠Included modules

php5-common
php5-json
php5-gd
php5-curl
php5-mcrypt
php5-mysqlnd
php5-sqlite
php5-apcu
php5-memcached
php5-xdebug

⁠Configuration

Any files under /app/config will be symlinked into the container's filesystem beginning at /etc/php5. This can be used to overwrite the container's default php fpm configuration with a custom, project specific configuration.

If you need a custom shell script to be run on start or stop (e.g. to set symlinks) you can do so by creating the file /app/config/up.sh or /app/config/down.sh.

⁠XDebug

This container comes with XDebug pre-installed but disabled. To enable it just port 9001:9001 to your docker_compose.yaml or your shell command and create a file named /app/config/php56/fpm/conf.d/20-xdebug.ini with the following content:

zend_extension=xdebug.so
xdebug.remote_enable=1
xdebug.remote_port="9001"
xdebug.remote_connect_back=1

Tag summary

Content type

Image

Digest

Size

411.9 MB

Last updated

almost 10 years ago

docker pull qoopido/php56