Speed up development with full-stack environments for every branch
SoMa, San Francisco
Joined May 2012
- Tweets1.5K
- Following114
- Followers1.6K
- Likes401
Runnable retweeted
Well, @GetRunnable is quite honestly the most amazing tool I've used all year. Well done. Kudos.
Runnable retweeted
Achieve practical end-to-end #E2E testing with #Docker Compose #Kubernetes and #Helm ow.ly/nHzg30cA6al
Runnable retweeted
Thanks everyone! A great discussion and a lot of gifs.. fun times! #dockerchat
Runnable retweeted
A10. another answer, automated test creation (prior to pipeline) #DockerChat
Runnable retweeted
A10. The developers (I didn't mean that @PeterNickolov; I swear!) #DockerChat
Runnable retweeted
A7. There are 3 manual steps: Reviewing the Code, End to End Testing and Deploying. #DockerChat
Runnable retweeted
A8. 1 minute with no dependency changes and about 10 minutes when we have to run #npm install #DockerChat – at San Francisco, CA
Runnable retweeted
A7. coding; reviewing; deploying. Hope we can automate the first one day ;)
#DockerChat – at San Francisco, CA
Runnable retweeted
A8. 5-10 mins depends on if we do perf. testing - really fast is my final answer #DockerChat
Runnable retweeted
Q7: Zero manual steps... unless you consider coding/checking in code a manual step. #dockerchat #searchingforagiftoolong
Runnable retweeted
Q6. They are pretty much the same #DockerChat – at San Francisco, CA
Runnable retweeted
A5: Deployment... we ended up building a system because of it. #shamelessplug datagridsys.com/nomorescript… #dockerchat
Runnable retweeted
Defining your dev environment with Compose is such an great way to simplify on boarding too. #dockerchat
Runnable retweeted
+1 compose or model driven creation is very important - one of our lessons learned as we went back to compose after not using it first.
Runnable retweeted
A4: #Docker = Speed. Seriously fast. Like 1 minute to deploy fast. #dockerchat