Docker based Development Setup - #165
Open
GALHP wants to merge 3 commits into
Open
Conversation
This was referenced Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Containerized local dev setup (Docker Compose +
maketargets) so clonio-clibuilds/runs/tests without a host PHP toolchain, and makes the
initIO-errortests pass under the container's root user.
Motivation
Contributors otherwise need a matching PHP 8.x + extensions setup. A throwaway
container removes that friction and gives everyone the same
composer test/composer lintenvironment.What's changed
compose.yaml— onephpservice (wodby/php:8.5), repo bind-mounted at/var/www/html,php -vhealthcheck.Makefile.dev.mk(+ hook inMakefile) —make up/down/restart/bash,make test(XDEBUG_MODE=coverage composer test),make check(
composer lint && composer test:types)..env.example—APP_KEY+DEV_PHP_VERSIONhint.tests/Feature/Commands/InitCommandTest.php— the two "cannot write .env"IO-error tests simulated a read-only disk with
chmod, a no-op under root(the container), so they failed there; they now mock
Storage::put()returningfalse— user-independent, same error path.Testing
make up && make test— full suite green in the container.