Lots of our people have lots of opinions. Here are just a few of them
ThoughtWorks embraces the individuality of the people in the organization and hence the opinions expressed in the blogs may contradict each other and also may not represent the opinions of ThoughtWorks.
In the first post on how we moved our application to Docker on AWS I described the reason for us to do it, and how we set up the servers. This post describes how we've organized the different Docker containers.
Our setup on AWS looks like this:
We use an EC2 load balancer to route traffic to our web hosts. This is an easy way to setup clustering, but you should be aware that EC2 does not allow for any alternative route or html page if no hosts are available. This means that if all…
The short answer (at least for the piece I’m interested in) is to recreate
gcheckout.sh that Google didn’t open-source. Refer how Googlers Subset their Trunk
At the time of writing, there are no issues for the Bazel Github project that talk about modifying a checkout based on needs or intents that are codified in BUILD files (here’s an example). Of course that’s not a universal SCM feature. Git has “sparse checkout”, but not sparse clone, and it’s impossible to use this in a monorepo configuration. Perforce and Subversion could do it. Perforce has client specs, and Google’s internal…
Last fall, we moved the Qwaya Facebook ads tool from a single host on Rackspace to a clustered Docker based environment on AWS. This is the first blog post of hopefully more that I'm writing to remember what we did. I've planned two more posts, one on how we handle CI and one on container orchestration.
The task at hand was not "Move to docker", it was "get out of single host hosting". The old deployment consisted of some quite complicated Fabric scripts that was run from an arbitrary developers laptop. The source code repository did not match…