php-zendserver official docker image

Zend Server - the integrated PHP application platform for mobile and web apps.

Supported tags and respective Dockerfile links

For more information about this image and its history, please see the relevant manifest file (library/php-zendserver) in the docker-library/official-images GitHub repo.

What is Zend Server?

Zend Server is the integrated application platform for PHP mobile and web apps. Zend Server provides you with a highly available PHP production environment which includes, amongst other features, a highly reliable PHP stack, application monitoring, troubleshooting, and the all-new Z-Ray. ###Boost your Development with Z-Ray Using Zend Server Z-Ray is akin to wearing X-Ray goggles, effortlessly giving developers deep insight into how their code is running as they are developing it – all without having to change any of their habits or workflow. With Z-Ray, developers can immediately understand the impact of their code changes, enabling them to both improve quality and solve issues long before their code reaches production. In addition to the obvious benefits of this ‘Left Shifting’ – better performance, fewer production issues and faster recovery times – using Z-Ray is also downright fun! ###Powering Continuous Delivery Zend Server is the platform that enables Continuous Delivery, which provides consistency, automation and collaboration capabilities throughout the application delivery cycle. Patterns are available to integrate Zend Server with: Chef, Jenkins, Nagios, Vmware, Puppet.

Additional Resources http://www.zend.com/ http://kb.zend.com/ http://files.zend.com/help/Zend-Server/zend-server.htm#faqs.htm http://files.zend.com/help/Zend-Server/zend-server.htm#getting_started.htm

PHP-ZendServer

This is a cluster-enabled version of a Dockerized Zend Server 7.0 container. With Zend Server on Docker, you'll get your PHP applications up and running on a highly available PHP production environment which includes, amongst other features, a highly reliable PHP stack, application monitoring, troubleshooting, and the new and innovative new technology - Z-Ray. Z-Ray gives developers unprecedented visibility into their code by tracking and displaying in a toolbar live and detailed info on how the various elements constructing their page are performing.

Usage

Launching the Container from Docker-Hub

Zend Server is shared on Docker-Hub as php-zendserver. - To start a single Zend Server instance, execute:

    $ docker run php-zendserver
  • You can specify the PHP and Zend Server version by adding ':' or ':-php' to the 'docker run' command. Availible PHP version are 5.4 & 5.5 (5.5 is the default) and Zend Server 7 (for example: php-zendserver:7.0-php5.4).

  • To start a Zend Server cluster, execute the following command for each cluster node:

    $ docker run -e MYSQL_HOSTNAME= -e MYSQL_PORT=3306 -e MYSQL_USERNAME= -e MYSQL_PASSWORD= -e MYSQL_DBNAME=zend php-zendserver

Launching the Container from Dockerfile

  • From a local folder containing this repo's clone, execute the following command to generate the image. The image-id will be outputted:

    $ docker build .
  • To start a single Zend Server instance, execute:

    $ docker run 
  • To start a Zend Server cluster, execute the following command on each cluster node:

    $ docker run -e MYSQL_HOSTNAME= -e MYSQL_PORT=3306 -e MYSQL_USERNAME= -e MYSQL_PASSWORD= -e MYSQL_DBNAME=zend 

Accessing Zend server

Once started, the container will output the information required to access the PHP application and the Zend Server UI, including an automatically generated admin password.

To access the container remotely, port forwarding must be configured, either manually or using docker. For example, this command redirects port 80 to port 88, and port 10081 (Zend Server UI port) to port 10088:

    $ docker run -p 88:80 -p 10088:10081 php-zendserver

For clustered instances:

    $ docker run -p 88:80 -p 10088:10081 -e MYSQL_HOSTNAME= -e MYSQL_PORT=3306 -e MYSQL_USERNAME= -e MYSQL_PASSWORD= -e MYSQL_DBNAME=zend 

Please note, that when running multiple instances only one instance can be bound to a port. If you are running a cluster, either assign a port redirect to one node only, or assign a different port to each container.

Env variables

Env variables are passed in the run command with the "-e" switch.

Optional env-variables:

To specify a pre-defined admin password for Zend Server use: - ZS_ADMIN_PASSWORD

MySQL vars for clustered ops. ALL are required for the node to properly join a cluster: - MYSQL_HOSTNAME - ip or hostname of MySQL database - MYSQL_PORT - MySQL listening port - MYSQL_USERNAME - MYSQL_PASSWORD - MYSQL_DBNAME - Name of the database Zend Server will use for cluster ops (created automatically if it does not exist).

To specify a pre-purchased license use the following env vars: - ZEND_LICENSE_KEY - ZEND_LICENSE_ORDER

Minimal Requirements

  • Each Zend Server Docker container requires 1GB of availible memory.

License

Zend Technologies Ltd.

Supported Docker versions

This image is officially supported on Docker version 1.6.2.

Support for older versions (down to 1.0) is provided on a best-effort basis.


Docker, Inc is the company behind the open source Docker platform and the growing Docker ecosystem of contributors, partners and adopters revolutionizing the way distributed applications are built, shipped, and run.



Website: docker.com





Copyright (c) 2014-2015 Docker, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Login to View or Leave Comments

Container
Converse with your fellow Users in the Automic Community.

Updated:
May 14, 2015