You can now run different PHP versions per project: Release v3.0.0-beta-0.1
7. 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
You can only enter the PHP container if it is running.
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
# Execute on the host operating system host> ./shell.sh # Now you are inside the PHP Linux container email@example.com in /shared/httpd $
On Windows you have a different script to enter the PHP container:
Just run it and it will enter you into the PHP container and bring you to
# Execute on the host operating system C:/Users/user1/devilbox> shell.bat # Now you are inside the PHP Linux container firstname.lastname@example.org in /shared/httpd $
When you enter the container with the provided scripts, you are doing so as the user
If you do need to perform any actions as root (such as installing new software), you can use
# Inside the PHP Linux container as user devilbox email@example.com in /shared/httpd $ sudo su - # Now you are root and can do anything you want firstname.lastname@example.org in /shared/httpd $
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.
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.
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.
This is just a short overview about the possibility to work inside the container. If you want to dig deeper into this topic there is also a more advanced tutorial available: