[Copilot]

This change adds first-class support for MySQL/MariaDB Unix socket connections in Redmine container configuration. When DB_SOCKET is provided (with DB_ADAPTER=mysql2), generated DB config now prefers socket-based connectivity over DB_HOST/DB_PORT while preserving current TCP behavior when unset.

• Runtime DB parameter handling

  • Added DB_SOCKET to runtime environment defaults.
  • Updated DB parameter finalization to allow MySQL socket-based config without requiring DB_HOST.

• database.yml generation behavior

  • Added socket templating support in the database config template.
  • In MySQL mode:
    • if DB_SOCKET is set: remove host/port keys from generated database.yml
    • if DB_SOCKET is unset: remove socket key
  • Keeps generated config mutually consistent and avoids mixed transport fields.

• MySQL connection checks and command safety

  • Updated MySQL readiness and isolation checks to use socket mode when configured.
  • Refactored command construction to array-based invocation for safe argument handling (spaces/special chars).
  • Kept PostgreSQL readiness path resolution robust (command -v first, fallback scan).

• Documentation updates

  • Added DB_SOCKET to the configuration reference.
  • Added a socket-based MySQL/MariaDB run example and clarified precedence semantics.

# Example env configuration (socket mode)
DB_ADAPTER: mysql2
DB_SOCKET: /var/run/mysqld/mysqld.sock
DB_NAME: redmine_production
DB_USER: redmine
DB_PASS: password

Generated database.yml (MySQL socket mode) now includes socket: and omits host:/port:.

• Fixes Feature request: Support for MySQL/MariaDB database socket configuration #602

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.