[treis]

> It spins up containers that simulate your tech stack, but it won't be an exact replica of your production infrastructure. For example, if you use a managed postgres DB in AWS in your prod environment, in a Dockup environment, you would use a postgres Docker container that's started using the official postgres image.

I don't quite understand this. Why wouldn't I want to spin up another postgres DB in AWS for testing?

I think that's what I'm a bit stuck on. Being able to spin up a test environment on demand is cool. But if I'm going through the effort to do that, why not go through the effort to do the same for a production environment? Then I can use the exact production configuration to run my tests.

[emilsoman]

Dockup does have support for this through a feature called "resource pools" which allows you to create external resources and use them in your dockup deployments. This is more involved than simply using the containers, but the support is there for those who think it's worth the effort. Thanks for asking!

[Waterluvian]

This is how I approached it. With ECS on AWS I could just make staging, production, and test envs all identical by deploying a set of containers.

But Docker for development really still feels so annoying and in the way. So I've just been using a Python virtualenv and a postgres instance installed directly on my machine. I tried to make docker dev work but it just always felt in the way, between my dev tools and the environment. It's been working fine but I'm sure there's some who will hand wave and insist this is a problem.