docker-build

To run a gate-checked Docker build, you must first execute the repository verification scripts before deployment. This ensures the Offerte service passes quality checks locally before proceeding to a manual remote deploy.

Enforcing a verification step before a manual Docker deployment requires running scripts/verify.sh and scripts/deploy.sh first. This quality-gated workflow removes guesswork by making verification a mandatory prerequisite for building and deploying.

Yes, you can use rsync for SSH-enabled remote Docker service deploys. The deployment workflow enforces rsync-based transfers to manually push the Offerte Docker service to remote servers after passing local build checks.

This Docker deployment workflow applies specifically to the aanvraag_offerte and jvdp-offerte repositories. It targets the Offerte Docker service exclusively rather than functioning as a generic Docker build helper.

Your Docker build requires running verification scripts first to enforce a quality-gated workflow. This mandatory step removes the risk of deploying unverified code by checking the repository state before any build or deploy action proceeds.

After a gated Docker deployment finishes, the system reports the executed commands, exit status, and verification evidence. This provides a clear audit trail confirming whether the Offerte service build and rsync deployment succeeded.