RES-2026 Switch CircleCI to use Docker Compose #805
Conversation
…laywright packages.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| name: Setup application | ||
| command: | | ||
| # Grant timezone access - run directly on MySQL container | ||
| docker exec restarters_db mysql -u root -ps3cr3t -e "GRANT SELECT ON mysql.time_zone_name TO 'restarters'@'%';" |
Check failure
Code scanning / SonarCloud
MySQL database passwords should not be disclosed High
| # Setup additional configuration needed for CI (most setup already done by docker_run.sh) | ||
| # Set MySQL function creators using session variable (compatible with MySQL 5.7) | ||
| docker exec restarters_db mysql -u root -ps3cr3t -e "SET GLOBAL log_bin_trust_function_creators = 1;" |
Check failure
Code scanning / SonarCloud
MySQL database passwords should not be disclosed High
| echo "Waiting for services in profile: {{.PROFILE}}" | ||
| echo "" | ||
| # Wait for core services (always needed) |
Check failure
Code scanning / SonarCloud
MySQL database passwords should not be disclosed High
…ssions we don't have in Docker Compose environment.
There was a problem hiding this comment.
Why are we dropping these triggers? I want these repair status strings available in various reporting environments, so would prefer them to remain in the live DB.
There was a problem hiding this comment.
They're no longer used on the client, and single source of truth is better than triggers. But if you use them elsewhere, then ok - I've removed the migration.
# Conflicts: # .circleci/config.yml # CLAUDE.md
|
We are moving to use Docker Compose for our dev environment. This PR switches our CircleCI automated testing to use that environment too.
Also includes some fixes to add some required PHP extensions and directories for image uploads.