Overview | Quickstart | Install | Update | Configure | Run | Usage | OS | Backups | Examples | Technical | Hacking | FAQ
- General
- Are there any differences between Linux, Windows and OSX?
- Why are mounted MySQL data directories separated by version?
- Why are mounted PostgreSQL data directories separated by version?
- Why are mounted MongoDB data directories separated by version?
- Why do the user/group permissions of log/ or cfg/ directories show 1000?
- Can I not just comment out the service in the .env file?
- Are there any required services that must/will always be started?
- What PHP Modules are available?
- Can I load custom PHP modules without rebuilding the Docker container?
- Configuration
- Can I change the MySQL root password?
- Can I add other PHP Modules?
- Can I change php.ini?
- Can I change my.cnf?
- Can I switch HHVM between PHP 5.6 and PHP 7 mode?
- Can I change the project virtual host domain .loc?
- Can I just start PHP and MySQL instead of all container?
- Do I always have to edit /etc/hosts for new projects?
- Usage
- Troubleshooting
Yes, have a look at OS to read up about the differences.
This is just a pre-caution. Imagine they would link to the same datadir. You start the devilbox with mysql 5.5, create a database and add some data. Now you decide to switch to mysql 5.7 and restart the devilbox. The newer mysql version will probably upgrade the data leaving it unable to start with older mysql versions.
See: Why are mounted MySQL data directories separated by version?
See: Why are mounted MySQL data directories separated by version?
Uid and Gid are set to 1000 by default. You can alter them to match the uid/gid of your current user. Open the .env file and change the sections NEW_UID and NEW_GID. When you start up the devilbox, the php-container will use these values for its user.
No, don't do this. This will lead to unexpected behaviour (different versions will be loaded).
The .env file allows you to configure the devilbox, but not to start services selectively.
Yes. http and php will automatically always be started (due to dependencies inside docker-compose.yml) if you specify them or not.
The devilbox is a development stack, so it is made sure that a lot of PHP modules are available out of the box in order to work with many different frameworks.
apc, apcu, bcmath, bz2, calendar, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imagick, imap, intl, json, ldap, libxml, magickwand, mbstring, mcrypt, memcache, memcached, mhash, mongodb, msgpack, mysql, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, phalcon, Phar, posix, pspell, readline, recode, redis, Reflection, session, shmop, SimpleXML, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, uploadprogress, wddx, xdebug, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib
There will however be slight differences between the versions and especially with HHVM. To see the exact bundled modules for each version visit the corresponding docker repositories on Github:
PHP 5.4 | PHP 5.5 | PHP 5.6 | PHP 7.0 | PHP 7.1 | PHP 7.2 | HHVM
Yes. You can load custom PHP modules for each PHP version separately. See Custom PHP Modules in the Configuration documentation.
Yes, you can change the password of the MySQL root user. If you do so, you must also set the new password in your .env file. See Configure for how to change the values.
Yes, if there are any PHP modules you require that are not yet available in the PHP Docker container, you can install it during run-time, or create your own container. See Hacking for more information.
Yes, php.ini directives can be changes on a per PHP version base. Go to ./cfg/ inside devilbox git diretory. There you will find configuration directories for each php version. Just put a *.ini file there and restart the devilbox.
Yes, my.cnf directives can be changes on a per MySQL version base. Go to ./cfg/ inside devilbox git diretory. There you will find configuration directories for each MySQL version. Just put a *.cnf file there and restart the devilbox.
Yes, this can be done by adding a *.ini file to ./cfg/hhvm-latest/ with the following content to disable PHP 7 mode:
hhvm.php7.all = 0The default is to use PHP 7 mode.
Yes, the .env variable TLD_SUFFIX can be adjusted with whatever domain or subdomain your require. A few examples to get you started:
| Project folder | TLD_SUFFIX | Project URL |
|---|---|---|
| project1 | loc | http://project1.loc |
| project1 | local | http://project1.local |
| project1 | dev | http://project1.dev |
| project1 | work.loc | http://project1.work.loc |
Yes, every Docker container is optional. The devilbox allows for selective startup. See Run: selective start for more detail.
You need a valid DNS entry for every project that points to the Httpd server. As those records don't exists by default, you will have to create them. However, the devilbox has a bundled DNS server that can automate this for you. The only thing you have to do for that to work is to add this DNS server's IP address to your /etc/resolv.conf. See Configure: AutoDNS for instructions.
Yes, see How to setup CakePHP.
Yes, see How to setup Drupal.
Yes, see How to setup Joomla.
Yes, see How to setup Laravel.
Yes, see How to setup Phalcon.
Yes, see How to setup Symfony.
Yes, see How to setup Wordpress.
Yes, see How to setup Yii.
Yes, see How to setup Zend.
When you change any paths inside .env that affect Docker mountpoints, the container need to be removed and re-created during the next startup. Removing the container is sufficient as they will always be created during run if they don't exist.
In order to remove the container do the following:
$ docker-compose stop
# Remove the stopped container (IMPORTANT!)
# After the removal it will be re-created during next run
$ docker-compose rm -f