k8s/Kubernetes>> docker-php>> 返回
项目作者： vtardia

项目描述 ：
Experimental set of Docker images for deploying PHP projects
高级语言： PHP
项目地址: git://github.com/vtardia/docker-php.git
创建时间： 2019-09-12T16:09:50Z
项目社区：https://github.com/vtardia/docker-php
开源协议：
下载


PHP/Docker

This repo contains an experimental set of Docker images for deploying PHP projects using Docker.

It was inspired by Demin Yin’s PHP UK 2019 talk Massively Scaled High Performance Web Services with PHP.

The image set includes:

  • a web server base image with Nginx, PHP-FPM, Composer and Supervisor
  • a worker base image with PHP CLI and Composer
  • a app example with a web frontend and a background worker

All images are based on Alpine GNU/Linux in order to be as small as possible, and have MySQL and MongoDB PHP extensions enabled.

Testing the example apps

1. Build the base images without username

  1. $ cd base/web && docker build . -t php-server:8.2-alpine; cd ../..
  1. $ cd base/worker && docker build . -t php-worker:8.2-alpine; cd ../..

2. Start the stack

  1. $ docker compose up --build [-d]

3. Check that all is working properly

The worker script should emit a log line every few seconds.

The web app listen by default on http://localhost:8000, it exposes this endpoints:

  • /: simple hello world
  • /info.php: shows PHP configuration
  • /mysql: connects to MySQL and fetches some sample data
  • /postgres: connects to Postgres and fetches some sample data

Simple and naive production scenario

Please note: I did my best to configure the images with a proper security level, but I haven’t yet tested them with an actual production environment, so if you want to use it in production take your time to test and tweak the system!

The scripts build/web and build/worker will package your web and console apps into Docker images adding a versioning tag based on the current commit hash. The latest version tag is saved into build/web.version and build/worker.version.

  1. REPOSITORY          TAG                  IMAGE ID            CREATED              SIZE
  2. app-worker          <CommitHash>         3f3f297562a6        About a minute ago   120MB
  3. app-web             <CommitHash>         d451986e42f5        2 minutes ago        170MB

The images can then deployed to either your private Docker registry (i.e. docker push app-web:<hash>) or directly to your production server using Docker save command:

  1. $ docker save app-web:<hash> | gzip > build/app-web-<hash>.tar.gz
  2. $ scp build/app-web-<hash>.tar.gz you@yourserver:/some/path/app-web-<hash>.tar.gz

On your production server you can then load the new image into Docker:

  1. $ ssh you@yourserver 'docker load -i /some/path/app-web-<hash>.tar.gz'
  2. $ scp build/web.version you@yourserver:/some/path/web.version

And start the new version using a script similar to the provided prod example, which reads the image tags from the .version files and set the needed environment variables.

  1. $ ssh you@yourserver 'cd /some/path && ./prod stop && ./prod start'

All this can be done manually or by a CI/CD solution like Bitbucket Pipelines or Github Actions.

SSL and Proxy

Although it may be tempting to embed SSL configuration and certificates within web images, it does make more sense to let them serve HTTP on a custom port (i.e. 8000) and have a frontend proxy as SSL endpoint on the deployment server. This technique also will allow to show a maintenance page during the short stop/start cycle on update.