Skip to content

cleverage/ui-process-bundle#99 - Allow running the demo on PostgreSQL instead of MySQL - #70

Merged
njoubert-cleverage merged 1 commit into
mainfrom
postgresql
Oct 5, 2026
Merged

njoubert-cleverage merged 1 commit into
mainfrom
postgresql

Conversation

@njoubert-cleverage

@njoubert-cleverage njoubert-cleverage commented Oct 5, 2026 •

Copy link
Copy Markdown
Member

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-postgres block and postgres service (healthcheck, port ${POSTGRES_PORT:-5432}), using the same process_bundle_demo_data volume as mysql
    • in the depends_on of php-fpm: postgres, to use instead of mysql
  • .docker/postgres/Dockerfile: postgres:${POSTGRES_VERSION:-16} image with the host UID / GID, as the mysql one
  • .env: its DATABASE_URL (postgresql://app:app@postgres:5432/app?serverVersion=16&charset=utf8), commented out
  • .docker/php/Dockerfile: pdo_pgsql extension (libpq-dev)
  • migrations/Version20241210154810.php: PostgreSQL branch for the author / book tables (the MySQL SQL is unchanged)
  • docs/postgresql.md: configuration when installing the project (comment mysql / uncomment postgres in the services and in the depends_on of php-fpm, DATABASE_URL in .env.local, make start), variables, psql; noted at the top of README.md and in docs/index.md

Checked 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.logger processes (finish, logs stored), UI login, launch from the UI consumed by the execute_process worker. 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

  • Documentation updates
    • Reference
    • Changelog
  • Unit tests

Breaking changes

None: MySQL stays the default database. The PHP image gets the pdo_pgsql extension.

🤖 Generated with Claude Code

… 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 njoubert-cleverage changed the title cleverage/ui-process-bundle#99 - Run the demo on PostgreSQL (commented out service); add demo.ui.entity_manager_clear cleverage/ui-process-bundle#99 - Allow running the demo on PostgreSQL instead of MySQL Oct 5, 2026
@njoubert-cleverage
njoubert-cleverage merged commit b88d2f2 into main Oct 5, 2026
17 checks passed
@njoubert-cleverage
njoubert-cleverage deleted the postgresql branch October 5, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant