/explore
|
You are here 
|
arveknudsen.com | ||
| | | | |
tricht.eu
At work we use AWS ECS (Amazon EC2 Container Service) for orchestrating our docker containers. We have a rather small number of containers running (26~) which all log to CloudWatch. Being unsatisfied by the features such as alerting we started looking for a better logging solution. |
|
| | | | | ||
| | | | |
tamas.dev
Keeping things simple When working on side projects I always try to keep things simple and focus on the important things at the beginning as delivering values is key. I don't want to deal with clusters, HA, pipelines etc. because it's more than alright to deploy to production from your laptop in the early days. In this particular example, the infrastructure is basically an RDS instance (no multi AZ at this point) and an EC2 box with Ubuntu and docker installed on it manually. The deploy process is a simp... |
|
| | | | | ||
| | | | |
leif.io
This last post is about bringing it all together. Right now we are at a point where we have random script snippets that executed in the right order will launch a service in the cloud. But we need to get this in a more structured way on a build server. As a CI provider I use CircleCI and Ive been waiting to try out their 2.0 version including workflows. As CircleCI heavily relies on Docker, we can just go ahead and use our base image for building. |
|
| | | | | ||
| | | | |
f5n.org
f5n.org - a personal website |
|
| | | |||
