FAQ

What do I need to use coldbrew-cli?

• Docker and AWS. More specifically...
  • Docker installed in your system
  • Either local Docker image to push or Dockerfile of your application
  • Your AWS access keys

What languages tech stacks does coldbrew-cli support?

• You can write your applications in any languages or tech stacks as long as it can be Docker-containerized.

Is coldbrew-cli free?

• Yes. Using coldbrew-cli to deploy Docker containers on your own AWS environment is completely free. Pretty obvious, but, you still have to pay for your AWS costs (like EC2 Instances, ELB Load Balancers, etc). There's nothing we can do about it.

Why did you make this tool?

• After building and running several production-level backend services using different tech stacks on different platforms like AWS (EC2/ECS), Google Cloud, Kubernetes, Mesos, etc for years, I saw some patterns that could be simplified and automated. And, as a developer, I always wanted a simple tool that lets me deploy my containers on a scalable server environment (which happen to be AWS most of the time in my case) using well-known best practices. DevOps work is really fun, but, at the end of the day, I always wanted to focus more on the application development side.
• Also I wanted to build the tool that does not involve too many high-level abstractions, because that typically comes with a learning curve and certain maintenance costs for the tool itself. I understand that's almost inevitable to support more complex use cases, but, I believe there can be a simple (but balanced) approach that can cover 80% (or even 90%) of such use cases. I'd like a tool that solves 90% of my problems and still does let me do the rest. I like the products from HashiCorp for that reason.

Which AWS regions does coldbrew-cli support?

• You can use coldbrew-cli in all AWS regions that support ECS.

How do I contribute to coldbrew-cli?

• Please make a pull request.

I need help!

• Please create an issue.