qjudge-env-compose-owner

Run Django migrations inside a Docker Compose container by using an environment-aware wrapper that maps main, dev, or test to the correct compose file and executes manage.py commands within the backend service, preventing host-level environment drift.

Executing pytest and npm scripts inside containers enforces an exec-first policy that standardizes the testing environment, reducing environment drift and test flakiness caused by differences between host and container dependencies.

Manage multiple Docker Compose files by using an environment selector that automatically maps dev and test environments to their respective compose files, then routes commands to the correct services like backend-test and frontend-test.

Yes, you need Docker Compose available on your host to execute environment-specific commands. The wrapper relies on this dependency to run scripts that manage service orchestration and execute commands inside the containers.

Collect logs from test-specific services by using a standardized wrapper that targets the test environment's compose file, allowing you to run docker compose logs against mapped services like backend-test and frontend-test for container debugging.

Yes, you can run npm scripts for frontend debugging in CI by targeting the test environment, which routes the execution inside the frontend-test container to ensure the scripts operate within the isolated Docker environment.