Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Dockup (YC W19) – On demand staging environments for dev teams

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 55 posts

Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams

#33

Post by emilsoman »

wasd wrote: post #31

Suppose my application is dependent on the subdomain like "customer1.wasdapp.com". Is your application able to spin up "customer1.wasdstaging.com"?

Yes, this is possible. By default Dockup would give a random subdomain to each deployment, but some of our customers wanted to use Dockup deployments for giving customer demos so we have added support for long lived deployments that use a specified subdomain.

Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams

#34

Post by emilsoman »

kevan wrote: post #32

I like it. Back in 2015 I built something similar[1] for my company and it helped us make the transition from time-bound releases with QA on mainline to per-PR QA and CI/CD. [1] https://medium.com/@kevanahlquist/dockerui-at-bluestem-2890b...

This looks neat! Thanks for sharing.

Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams

#36

Post by emilsoman »

aboutruby wrote: post #35

How does it compare to Heroku review apps?

Dockup is like Heroku review apps, but for the entire tech stack (each PR gets a dedicated environment with all the microservices in your stack). One benefit of using Dockup is that seeding DBs with prod-like data is easy and works super fast so you don't have to wait around for a long time until you do a pgdump/restore. We can do this in Dockup because we maintain a pool of single-use DBs for your deployments.

Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams

#37

Post by 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.

Post reply on HN