Might be useful for anyone who hasn't heard of Docker yet.
Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
21–30 of 55 posts
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#22Congrats on the launch! Any relation to Stream [0]? Your logo is very similar.
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#23I'm confused why I'd use this. My flow now is: 1. branch off of master 2. write a bunch of code that runs the risk of breaking stuff 3. deploy it to our already existing developer/staging environment 4. test it. if it is good, promote it to QA/UAT/CAT does Dockup assume that companies don't already have the 3 main environments (dev/CAT/prod) set up? Why would my service be worth anything in isolation? Usually when I…
This was a constant pain point for us as the engineering team grew. With a single staging environment, we could only have one changeset tested at a time. We built a tool like this internally and the engineers love it. When you have 20 feature going out in a week, it's not reasonable to have to wait for staging or qa to be available. We happened to call this 'review apps' but it's based on a similar principle. You can…
We would love to interview you to understand your experience, can you please drop me a mail here: emil@getdockup.com? Btw, we had the exact same requirement too - be able to test how a related change in multiple apps would affect the whole system. Check out our deployment form that helps us do this now: https://user-images.githubusercontent.com/1707078/53836663-6...
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#24Congrats on the launch! Any relation to Stream [0]? Your logo is very similar. 0: https://getstream.io/
Thank you! We had no idea about Stream, yes the logo does look very similar haha
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#25I'm confused why I'd use this. My flow now is: 1. branch off of master 2. write a bunch of code that runs the risk of breaking stuff 3. deploy it to our already existing developer/staging environment 4. test it. if it is good, promote it to QA/UAT/CAT does Dockup assume that companies don't already have the 3 main environments (dev/CAT/prod) set up? Why would my service be worth anything in isolation? Usually when I…
Step 3 in this flow is sometimes painful for big teams because developers have to wait in line if other developers are already using staging and may have to roll back databases after testing. Dockup gives the reviewer a chance to quickly test the feature without having to manually do deployments or start the app before merging the PR. Thanks for asking!
Yea, I agree. Step 3 is not a trivial setup for early-stage startups. Glad to see devtools companies trying to tackle this.
At the company I worked at, we built something similar using Heroku free dynos :) So that you can tag a PR and it automatically created a staging app using free Heroku dyno, it even came with a free database. The setup works but also quite spotty.
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#26This is great. Setting up proper staging environments has been on our procrastination list for a long time and as a small team, we haven't invested engineering hours for a real setup yet. If this simplifies the process so much that we barely need to think about it, I totally get the value.
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#27We have our own version of this -- we're fully remote, so it's an important thing to have. Basically we can deploy a full on-demand env with a single command. It's very useful.
(Really, you just launched exactly the same features what we have already internally. :) )
Good luck.
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#28We have our own version of this -- we're fully remote, so it's an important thing to have. Basically we can deploy a full on-demand env with a single command. It's very useful. (Really, you just launched exactly the same features what we have already internally. :) ) Good luck.
That's awesome! We would love to interview you to understand your experience, can you please drop me a mail - emil@getdockup.com?
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#29This is great. Setting up proper staging environments has been on our procrastination list for a long time and as a small team, we haven't invested engineering hours for a real setup yet. If this simplifies the process so much that we barely need to think about it, I totally get the value.
That's exactly our goal - teams that don't have the time to invest in devops should be able to use Dockup and not have to think much about it. Thanks for the kind words, glad you see the value here!
Re: Launch HN: Dockup (YC W19) – On demand staging environments for dev teams
#30How 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 been very happy with it. There are some interesting problems on demand environments create that persistent environments don't have, like data seeding for your apps (as naive state is an env comes up blank), extracting secrets/keys/credes/certs from the env now that they are different everytime you deploy etc. We have patterns for these problems now and has really forced us to mature our process.