Docker
Docker deployment experience at Duffion spans services with different runtimes and dependencies. Quark combines Python orchestration, its browser interface, model services and supporting infrastructure; Duffion’s website runs as a containerized WordPress stack.
Deployment is more than an image
A useful container setup includes persistent storage, service boundaries, health checks, and a repeatable release process. Backups and recovery need their own verification; a running container is only one part of acceptance.
What I build with it
- Containerized application and supporting services
- Persistent volumes and explicit network boundaries
- Repeatable builds, health checks, and scoped releases
- Backup, restore, and rollback procedures
Explore the Quark case study for the implementation behind these capabilities.
Docker deployment experience: planning a similar project
A deployment review should distinguish files inside an image from data that must survive its replacement. Identify the database, uploaded files and configuration needed to restore the application. Then record how a release is checked from a user’s perspective. The Quark and WordPress examples show why container packaging is part of a release process rather than the complete acceptance test.
For a new project or changes to an existing system, explore ongoing website and software development.