Repository navigation
cleverage/ui-process-bundle#99 - Allow running the demo on PostgreSQL instead of MySQL - #70
Merged
Merged
Conversation
Merged
2 of 3 tasks
… instead of MySQL - .docker/compose.yaml: postgres service (commented out), using the same process_bundle_demo_data volume as mysql; php-fpm depends_on to switch; .env: its DATABASE_URL, commented out - .docker/postgres/Dockerfile: postgres image with the host UID / GID, as the mysql one - .docker/php/Dockerfile: pdo_pgsql extension - migrations/Version20241210154810.php: PostgreSQL branch for the author / book tables - docs/postgresql.md: how to configure it when installing the project; README.md, docs/index.md: link to it Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
njoubert-cleverage
force-pushed
the
postgresql
branch
from
October 5, 2026 13:46
f5c32a6 to
d860595
Compare
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.
Description
Allow running the demo on PostgreSQL instead of MySQL, for cleverage/ui-process-bundle#99 (migrations fixed on PostgreSQL by cleverage/ui-process-bundle#100). MySQL stays the default database; the database is chosen when installing the project, before the first
make start..docker/compose.yaml, all commented out:x-base-postgresblock andpostgresservice (healthcheck, port${POSTGRES_PORT:-5432}), using the sameprocess_bundle_demo_datavolume asmysqldepends_onofphp-fpm:postgres, to use instead ofmysql.docker/postgres/Dockerfile:postgres:${POSTGRES_VERSION:-16}image with the host UID / GID, as themysqlone.env: itsDATABASE_URL(postgresql://app:app@postgres:5432/app?serverVersion=16&charset=utf8), commented out.docker/php/Dockerfile:pdo_pgsqlextension (libpq-dev)migrations/Version20241210154810.php: PostgreSQL branch for theauthor/booktables (the MySQL SQL is unchanged)docs/postgresql.md: configuration when installing the project (commentmysql/ uncommentpostgresin the services and in thedepends_onofphp-fpm,DATABASE_URLin.env.local,make start), variables,psql; noted at the top ofREADME.mdand indocs/index.mdChecked with a fresh installation following
docs/postgresql.md(isolated copy of the project, separate Docker project and volume):make start(images built, PostgreSQL 16 container running with the host UID, 8 migrations, fixtures),demo.doctrine.database.*/demo.doctrine.entitymanager.*/demo.loggerprocesses (finish, logs stored), UI login, launch from the UI consumed by theexecute_processworker. The default MySQL installation still runs.Merge once a release of cleverage/ui-process-bundle includes cleverage/ui-process-bundle#100 (the demo requires
^3.0: with v3.0.2, the migrations fail on PostgreSQL; MySQL is not affected).Requirements
Breaking changes
None: MySQL stays the default database. The PHP image gets the
pdo_pgsqlextension.🤖 Generated with Claude Code