A MODX Revolution test fixture for DDEV's
automated modx project-type tests (TestDdevFullSiteSetup in
pkg/ddevapp/ddevapp_test.go).
- MODX version: Revolution 3.2.1-pl (traditional distribution, with
core/vendor/committed) - Docroot: project root (
"") - Default admin login:
admin/Admin123!Admin
The ddev-automated-test branch is the default branch. It holds the full MODX
codebase (including Composer dependencies in core/vendor/) but not the
environment-specific pieces:
core/config/config.inc.phpis not committed — DDEV generates a#ddev-generatedversion onddev start.core/cache/is emptied..ddev/is not committed.config.core.php(root,manager/,connectors/) uses the portable distribution default (dirname(__FILE__) . '/core/'), so the codebase works at any mount path.
git clone -b ddev-automated-test https://github.com/ddev/test-modx
cd test-modx
ddev config --project-type=modx
ddev start
ddev launch # front end
ddev launch /manager/ # backend (admin / Admin123!Admin)The database and uploaded-files fixtures are attached to each tagged release:
db.sql.tar.gz— a MariaDB dump of the installed site (imported withddev import-db)files.tgz— the contents ofassets/includinguploads/ddev.png(imported withddev import-files)
The database and files artifacts are rebuilt with ./build-fixtures.sh, which
downloads the MODX traditional distribution, installs it non-interactively
against a throwaway MariaDB container using MODX's CLI installer, and exports the
db.sql.tar.gz and files.tgz artifacts into .tarballs/. See that script for
the exact commands.
- Update the code on the
ddev-automated-testbranch and commit. - Run
./build-fixtures.shto regenerate.tarballs/db.sql.tar.gzand.tarballs/files.tgz. - Tag the commit (for example
v3.2.1) and create a GitHub release. - Attach
db.sql.tar.gzandfiles.tgzto the release. - Point the
TestPkgModxentry in DDEV'spkg/ddevapp/ddevapp_test.goat the new tag.