4 ms·
They kind of have it[0] with ECS deployments but it’s being retired in November. [0] https://docs.docker.com/cloud/ecs-integration/ https://docs.docker.com/clo
by siquick 3y ago
They kind of have it[0] with ECS deployments but it’s being retired in November.
[0] https://docs.docker.com/cloud/ecs-integration/ https://docs.docker.com/cloud/ecs-integration/
- cookiengineer 3y agoThe issue I had with the EC2 deployment workflow was that it needed the AWS CLI configured, so it relied totally on AWS'es locked in workflow. I was thinking more of the lines as a standard API/set of protocols that works on the NAT-scale automatically. Humans are bad at guessing resources, and having people tweak all their VMs all the time with crappy code and crappy APIs is kinda the weakness of all dyno based workflows nowadays. All the "web scale" jokes have a core truth in them, and are actually not so funny for a reason :-/ But relying on a standard set of NAT rules and relationships, which the Dockerfile already provides, could make this an advantage instead.