## Running Pets on Docker for Mac/Windows in Development
Docker Swarm can easily be set up to run applications on a single developer laptop. The full app can be brought up to run in the same way it would run in production. We use a compose v3 file to deploy a fully fault tolerant frontend and backend, along with the configurations, secrets, and networks required for the application to run.
pets
This is the full architecture that is deployed when using [pets-dev-compose.yml](https://github.com/mark-church/docker-pets/blob/master/pets-dev-compose.yml).
This is the full architecture that is deployed when using [pets-dev-compose.yml](https://github.com/dockersamples/docker-pets/blob/1.0/pets-dev-compose.yml).
@@ -85,15 +85,15 @@ The `web` container has several configuration parameters as environment variable
## Running Ppetsets on Docker UCP in Production
This [full length tutorial](https://github.com/mark-church/docker-pets/blob/master/DEMO-DDC.md) will show you how to deploy and demo DDC with the pets app.
This [full length tutorial](https://github.com/docker/dcus-hol-2017/tree/master/docker-enterprise) will show you how to deploy and demo DDC with the pets app.
Production apps have entirely different requirements when it comes to security, deployment, and also security. Fortunately, deployment on Swarm & UCP is very much the same from development to production. Some minor additions to our compose file add in capabilities for secrets and also for L7 load balancing.
This is the full architecture that is deployed when using [pets-prod-compose.yml](https://github.com/mark-church/docker-pets/blob/master/pets-prod-compose.yml).
This is the full architecture that is deployed when using [pets-prod-compose.yml](https://github.com/dockersamples/docker-pets/blob/1.0/pets-prod-compose.yml).