You can now run different PHP versions per project: Release v3.0.0-beta-0.1
This example will use
composer to install Zend from within the PHP container.
composer requires the underlying file system to support symlinks. If you
use Docker Toolbox you need to explicitly allow/enable this.
See below for instructions:
- Docker Toolbox and Symlinks
Table of Contents
The following configuration will be used:
|Project name||VirtualHost directory||Database||TLD_SUFFIX||Project URL|
- Inside the Devilbox PHP container, projects are always in
- On your host operating system, projects are by default in
./data/www/inside the Devilbox git directory. This path can be changed via HOST_PATH_HTTPD_DATADIR.
It will be ready in six simple steps:
- Enter the PHP container
- Create a new VirtualHost directory
- Install Zend via
- Symlink webroot directory
- Setup DNS record
- Visit http://my-wp.loc in your browser
1. Enter the PHP container¶
All work will be done inside the PHP container as it provides you with all required command line tools.
Navigate to the Devilbox git directory and execute
shell.bat on Windows) to
enter the running PHP container.
2. Create new vhost directory¶
The vhost directory defines the name under which your project will be available.
<vhost dir>.TLD_SUFFIX will be the final URL ).
firstname.lastname@example.org in /shared/httpd $ mkdir my-zend
3. Install Zend via
Navigate into your newly created vhost directory and install Zend with
email@example.com in /shared/httpd $ cd my-zend firstname.lastname@example.org in /shared/httpd/my-zend $ composer create-project --prefer-dist zendframework/skeleton-application zend
How does the directory structure look after installation:
email@example.com in /shared/httpd/my-zend $ tree -L 1 . └── zend 1 directory, 0 files
4. Symlink webroot¶
Symlinking the actual webroot directory to
htdocs is important. The web server expects every
project’s document root to be in
<vhost dir>/htdocs/. This is the path where it will serve
the files. This is also the path where your frameworks entrypoint (usually
Some frameworks however provide its actual content in nested directories of unknown levels. This would be impossible to figure out by the web server, so you manually have to symlink it back to its expected path.
firstname.lastname@example.org in /shared/httpd/my-zend $ ln -s zend/public/ htdocs
How does the directory structure look after symlinking:
email@example.com in /shared/httpd/my-zend $ tree -L 1 . ├── zend └── htdocs -> zend/public 2 directories, 0 files
As you can see from the above directory structure,
htdocs is available in its expected
path and points to the frameworks entrypoint.
When using Docker Toolbox, you need to explicitly allow the usage of symlinks. See below for instructions:
- Docker Toolbox and Symlinks
5. DNS record¶
If you have Auto DNS configured already, you can skip this section, because DNS entries will be available automatically by the bundled DNS server.
If you don’t have Auto DNS configured, you will need to add the following line to your
host operating systems
/etc/hosts file (or
C:\Windows\System32\drivers\etc on Windows):
6. Open your browser¶
Open your browser at http://my-zend.loc or https://my-zend.loc
Once everything is installed and setup correctly, you might be interested in a few follow-up topics.
Use bundled batteries¶
The Devilbox ships most common Web UIs accessible from the intranet.
Enhance the Devilbox¶
Go ahead and make the Devilbox more smoothly by setting up its core features.
In case your framework/CMS requires it, attach caching, queues, database or performance tools.
Stay inside the container and use what’s available.