The application is composed of:
Use the documentation in this repository, including the QA check reference. Read the files from the same source revision as the application; the historical wiki is not maintained with the code.
Please report any issues in the QC tool via GitHub:
Use current supported Docker Engine and Docker Compose. Follow the deployment guide for reviewed image digests, secrets, HTTPS ingress and explicit database initialization, or the local workflow for development.
Each maintained deployment profile is one complete Compose file. Choose
docker/docker-compose.eea.yml for named volumes
or docker/compose.eea-storage.yaml for
operator-provisioned Azure/EEA host storage, and select that file alone. Local
and SQLite/provider profiles are self-contained too. A private environment file
supplies deployment values; no additional Compose file, generator or wrapper is
required. Rancher importer/version prerequisites still require verification on
the target deployment, as described in the deployment guide.
The maintained profiles select a canonical separated storage layout. New
qc_tool_v3_* application volumes and postgres17_data_v3 retain older volumes
without adopting their data. Workers read incoming deliveries, specifications
and boundaries through read-only mounts; private frontend state and submitted
publications are absent from worker mounts. See
storage paths and handoff.
Production startup checks a matching schema read-only. An entirely empty new
installation needs an explicit database plan|apply|check procedure and a
separately created administrator; starting Compose does not initialize it.
Never point PostgreSQL 17 at an existing PostgreSQL 14 data directory or reset
an occupied database to make a deployment start. Preserve the old database and
files until a separate logical restore and coordinated file handoff are verified.
For Windows host setup, see Windows notes.
If you want to propagate your local source code into running containers you may apply docker bind mount.
Such a way you overlay the source code already built in the image at /usr/local/src/copernicus_quality_tools.
For configuration advice, see the deployment guide.
There are already some automated tests at src/qc_tool/test.
See the instructions in NOTES.txt.
Maintainer commands are grouped by purpose under scripts/.
The catalog distinguishes repeatable tests, manual diagnostics and historical
experiments, and lists proposed removals. See the testing guide
for the host, worker and frontend suites.
The application-wide database package lives in
src/qc_tool/database/. The current 3.0.0 includes migration management, with committed native
Django migrations and an explicit candidate-only transition from the exact
supported history-free schema of earlier 3.0.0 installations. Future 3.0.1 and
3.1.0 releases extend this history with reviewed forward migrations. database plan|check inspect readiness without modifying it;
database apply initializes an entirely empty target and leaves a current managed
schema unchanged. Startup never applies pending migrations.
Admin migrations follow ready maintenance, full backup, separate restored candidate, installed migrations, verification and explicit switch. Database records and retained specification/delivery/report/publication files are verified together; files keep their original bytes and identities. Previous database, backup and file pins remain available for recovery. See the migration runbook before changing models, selecting persistent volumes or deploying. Legacy conversion remains private manual operator work outside the maintained application.
The demonstration service is publicly available at: https://qc-copernicus.eea.europa.eu/. Access credentials are managed by the service operator and are intentionally not stored in this repository.
The product catalog starts empty. Administrators upload selected JSON specifications through Products → Upload specification, then assign their products to users. The product_definitions directory contains reference QC recipes; startup does not import them. Each JSON file contains a list of parameterized checks. See Managing product specifications.
Content type
Image
Digest
sha256:b113a142b…
Size
134.6 MB
Last updated
about 3 hours ago
docker pull eeacms/copernicus-qctool-frontend