PROVIDER - The widest PHP version matrix in containers

Devilbox

Devilbox combines versions of 5 service families from 1 .env file, covering PHP 5.2 through 8.x with automatic virtual hosts and 100+ combinable options; the boundaries are a GUI-free workflow, large image footprint and a slower release cadence.

Developer Tools Germany 2026.11.19
3.7pts

Detailed Notes

Pros 5 items

Combines versions of 5 service families - PHP, MySQL, MariaDB, PostgreSQL and MongoDB - from 1 .env file
Covers a wide PHP range from 5.2 through 8.x for validating legacy projects
Creates 2 conveniences - custom TLDs and automatic virtual hosts - so dropping a project in a directory is enough
Provides 100+ combinable version options spanning many development and test scenarios
Fully open source with 0 cloud dependencies, runnable offline

Cons 4 items

Ships configuration and orchestration only, without a GUI or guided setup
Many images mean a large first pull and notable disk usage
Community cadence is slow, so new PHP versions lag behind
Troubleshooting requires Docker Compose and container log familiarity

Service Overview

Devilbox is an open source PHP development environment built on Docker Compose, known for its version matrix: nearly any combination of PHP and database versions switches through one configuration file.

In the development tools category it is the extreme-compatibility local environment: when a team must validate PHP 5.x legacy code and the newest release side by side, Devilbox's coverage is the main draw.

Key Strengths

  • Very wide version range: PHP 5.2 through 8.x
  • Free combination: 1 .env decides every service version
  • Automatic hosts: drop a project in and browse it
  • Rich options: 100+ combinable versions
  • Fully offline: no cloud dependency, data stays local

Product Ecosystem

Platform capabilities

Service version combinations, virtual host generation, custom TLDs, SSL generation, log inspection and container orchestration.

Integrations

Works with Docker Compose, Composer, phpMyAdmin, Adminer, Mailhog and mainstream IDEs.

Typical scenarios

Legacy PHP maintenance, multi-version compatibility checks, teaching demos and offline development.

Limitations

  • No GUI: everything happens through configuration
  • Disk footprint: pulling many images adds up
  • Slow cadence: new PHP versions arrive late
  • Troubleshooting depth: container logs and networking required

Use Cases

  • Multi-version compatibility checks (★★★★☆): the matrix shines
  • Maintaining legacy projects (★★★★☆): old PHP versions reproducible
  • Teaching and experiments (★★★☆☆): configuration-first thinking
  • Turnkey experience (★★☆☆☆): DDEV or Herd are easier

Pricing

Item Price Notes
Devilbox itself $0 MIT open source, commercial use allowed
Images and disk Local cost Driven by the number of versions pulled
Commercial support None GitHub issues only

FAQ

Should I choose Devilbox or DDEV?

Devilbox wins when many historical versions must be covered; DDEV is better for daily work with stronger docs and usability.

How do I switch PHP versions?

Change the PHP_SERVER variable in .env and restart the containers.

Is HTTPS supported?

Yes, enable the built-in certificate generation flow and trust the certificate in the browser.

Can the team share the configuration?

Yes, commit the non-sensitive parts of .env so everyone runs the same environment.

Code Examples

# Clone and start
git clone https://github.com/cytopia/devilbox.git
cd devilbox
cp env-example .env

# Choose PHP and database versions, then start
# Set PHP_SERVER=8.2 and MYSQL_SERVER=8.0 in .env
docker compose up -d

# Inspect containers and logs
docker compose ps
docker compose logs -f php
# Key .env entries (excerpt)
PHP_SERVER=8.2
MYSQL_SERVER=8.0
HTTPD_SERVER=nginx-stable
TLD_SUFFIX=loc

Community & Resources

Visit Devilbox Website → https://github.com/cytopia/devilbox
Visit Website ↗