This seems like a great tool for companies that don't have time to invest in dev ops.
Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
41–50 of 55 posts
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#42> 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…
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.
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#43As it is relevant .. plugging-in my own startup, platform.sh We do this with another twist ... our per-branch ephemeral staging clusters contain a full snapshot of production data. We believe strongly in immutability so what you are running in production is precisely what you tested in QA... And because production cloning relies on copy-on-write primitive it is basically immediate (think more in the dozens of seconds rather than multiple of minutes).
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#44> 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…
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!
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#45As it is relevant .. plugging-in my own startup, platform.sh We do this with another twist ... our per-branch ephemeral staging clusters contain a full snapshot of production data. We believe strongly in immutability so what you are running in production is precisely what you tested in QA... And because production cloning relies on copy-on-write primitive it is basically immediate (think more in the dozens of seconds…
It looks like I need to host my prod environment completely on your tool to make use of the staging feature. I will look more into this though, thanks for sharing. One difference is that in Dockup, we can boot up databases instantly with obfuscated prod like data and we do this because Dockup deployments are accessible by the entire team.
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#46How is it different from Heroku Review apps? (https://devcenter.heroku.com/articles/github-integration-rev...)
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#47Congrats on the launch! Any relation to Stream [0]? Your logo is very similar. 0: https://getstream.io/
[deleted]
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#48Congrats on the launch! Any relation to Stream [0]? Your logo is very similar. 0: https://getstream.io/
Logo "designer" here. That's an uncanny, unfortunate resemblance. All those hours taking pictures of a paper boat to redraw it seem so wasteful now :'|
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#49I always thought that the 'W' in YC batch numbers stood for 'winter', or isn't it? Or is 'W19' in the title a typo and should it be 'W18'?
I think that the batches are named based on when they're due to finish YC
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#50How do you feel you compare to the similar features in Gitlab’s product?
Yeah first thing I thought of was Gitlab environments / "review app" concept when reading this, we tried using Gitlab environments and ended up rolling our own on top of Kubernetes as it seems like an under-loved area of their product with a few warts. On demand envs for teams is a incredibly liberating experience for people who have been tied down to a single or small number of environments forever, our devs have be…
Hey there, product manager at GitLab for review apps here. I'd love to hear about the warts that you ran into that caused you to move to k8s. We're always working on improving the product and feedback like yours is really the most valuable thing for us.