KenCochrane

Code available here: https://github.com/akuity/argocd-mcp

Here is a link to a youtube video that explains it some more. https://www.youtube.com/watch?v=0GD63adFy7g

For those who don’t pay for a business insider account: http://archive.today/XGUl3

Hey Nick, it has been to long, I hope you are doing well. :)

I think they are similar but a little different. From Dagger's website "Dagger is a programmable CI/CD engine that runs your pipelines in containers" Kargo is a tool that works with your existing CI and CD (Argo CD) to help promote your code from one stage (Dev, UAT, QA, Prod, etc) to the next.

Kargo has native support for Argo CD today, but one of it's goals is to be agnostic and could probably work with Dagger or other tools in the future.

For those who are curious here is the Github repo https://github.com/akuity/kargo

Maybe I missed something, but how do you handle the fact that your nginx server is a single point of failure? If that goes down, traffic can’t get to your web servers.

Do you have more than one, and DNS load balance, or do you just live with the risk?

One of the main reasons why I use an ALB/ELB is so that I don’t have that SPOF. If you found a way around that, please share, I would love to know, so I can save some money :)

Too bad they didn't list the pricing, it would be nice to know how much it will cost, once released.

That's pretty cool, I have been thinking of building something similar, but for Python. How hard is it to add new languages?

What is the tech stack?

Does it cost much to keep it running?

Related blog post from Docker: https://blog.docker.com/2017/05/introducing-docker-new-ceo/

Have you looked at Docker for AWS yet? https://www.docker.com/aws

It will setup your swarm, which uses auto scaling groups for the worker nodes. You can then configure the auto scaling groups how ever you want, to scale based on your cloudwatch metrics, etc.

There is also a Docker for GCP product in beta. https://beta.docker.com but I don't know how auto scaling works for it.

Disclaimer: I work at Docker on the Docker for AWS product.

This project looks pretty popular and they are using a URL based API, maybe you can copy their URL structure.

http://thumbor.readthedocs.io/en/latest/

> I'm supporting images that end in .jpg, .png, or .gif. So currently I know that anything after the extension is parameters.

How do you know that is the extension and not a directory with a .jpg in the name? It is too complicated to convert to your URL scheme.

For me the URL based solution isn't quicker to type since I have to think too much. Also, how often is this going to be typed by hand verse scripted anyway? It will be easier to script if the URL is the same and only the GET Params change.

I prefer the get parameters, it is more obvious.

Another option that isn't as clean, but I have seen before is to Base64 encode the image URL. You wouldn't be able to easily type but you could keep your URL scheme, and still possible to script.

It doesn't mention this in the article, but I assume they got paid by Trend Micro for their work? Bug bounties, etc. If so, I wonder how much they made?

Here is a follow up blog post with more details about containerd: https://blog.docker.com/2016/12/containerd-core-runtime-comp...

What a small world, I worked with Greg at CashStar where he started the fork of django-money. I still remember the conversation we had in a meeting if we should fork the project or push our PR upstream to fix the issues we found. I'm glad our upstream PR started a trend to keep the library going. This is why I like open source, when you no longer need something you can hand it off to someone else who can take over, and let the code live on.