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
- php55
- initialize.sh (if needed)
- fpm
- php.ini (if needed)
- conf.d
- ...
- htdocs
- data
- php55
- sessions
- logs
php:
image: qoopido/php55:latest
ports:
- "9000:9000"
volumes:
- ./htdocs:/app/htdocs
- ./config/php55:/app/config
- ./data/php55:/app/data
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/php55:latest
php5-common
php5-json
php5-gd
php5-curl
php5-mcrypt
php5-mysqlnd
php5-sqlite
php5-apcu
php5-memcached
php5-xdebug
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.
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/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
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent