Enter the PHP container

Another core feature of the Devilbox is, to be totally independent of what you have or have not installed on your host operating system.

The Devilbox already ships with many common developer tools which are installed inside each PHP container, so why not make use of it.

The only thing you might need to install on your host operating system is your favourite IDE or editor to actually start coding.

If you want to find out what tools are available inside the PHP container, visit the following section: available_tools.

Table of Contents

local

How to enter

Note

You can only enter the PHP container if it is running.

Linux and MacOS

On Linux and MacOS you can simply execute the provided shell script: shell.sh. By doing so it will enter you into the PHP container and bring you to /shared/httpd.

# Execute on the host operating system
host> ./shell.sh

# Now you are inside the PHP Linux container
devilbox@php-7.0.19 in /shared/httpd $

Windows

On Windows you have a different script to enter the PHP container: shell.bat. Just run it and it will enter you into the PHP container and bring you to /shared/httpd.

# Execute on the host operating system
C:/Users/user1/devilbox> shell.bat

# Now you are inside the PHP Linux container
devilbox@php-7.0.19 in /shared/httpd $

How to become root

When you enter the container with the provided scripts, you are doing so as the user devilbox. If you do need to perform any actions as root (such as installing new software), you can use the password-less sudo.

# Inside the PHP Linux container as user devilbox
devilbox@php-7.0.19 in /shared/httpd $ sudo su -

# Now you are root and can do anything you want
root@php-7.0.19 in /shared/httpd $

Note

As this action is inside a Docker container, there is no difference between Linux, MacOS or Windows. Every host operating system is using the same Docker container - equal accross all platforms.

Directory mapping

One thing you should understand is the relation between the directories on your host operating system and the corresponding directory inside the PHP container.

The location of the data directory (env_httpd_datadir) on your host computer is controlled via the HOST_PATH_HTTPD_DATADIR variable inside the .env file. No matter what location you set it to, inside the container it will always be mapped to /shared/httpd.

See the following table for a few examples:

	Host operating system	Inside PHP container
Data dir	`./www/data`	`/shared/httpd`
Data dir	`/home/user1/www`	`/shared/httpd`
Data dir	`/var/www`	`/shared/httpd`

Tools

What is available

There are lots of tools available, for a full overview see available_tools. If you think you are missing a tool, install it yourself as root, or open up an issue on github to get it backed into the Docker image permanently.

available_tools

How to update them

There is no need to update the tools itself. All Docker images are rebuilt every night and automatically pushed to Docker hub to ensure versions are outdated at a maximum of 24 hours.

The only thing you have to do, is to update the Docker images itself, simply by pulling a new version.

getting_started_update_the_docker_images

Checklist

You know how to enter the PHP container on Linux, MacOS or Windows
You know how to become root inside the PHP container
You understand the directory relation between inside the container and your host operating system
You know how to update the tools by pulling new versions of the Docker images

4.2 KiB Raw Blame History