tiangolo / blog-posts

Blog posts and related code by Sebastián Ramírez (@tiangolo)

Hey! I'm @tiangolo (Sebastián Ramírez) 👋

I'm a software developer from Colombia. 🇨🇴

I currently live in Berlin, Germany. 🇩🇪

I have been building APIs and tools for Machine Learning and data systems, in Latin America, the Middle East, and now Europe, with different teams and organizations. 🌎

I created FastAPI, Typer and a bunch of other open source tools. 🚀

I like to build things with Deep Learning/Machine Learning, distributed systems, SQL and NoSQL databases, Docker, Python, TypeScript (and JavaScript), modern backend APIs, and modern frontend frameworks. 🤖

I'm currently dedicating a high percentage of my time to FastAPI, Typer, and my other open source projects. At the same time, I'm also helping a limited number of teams and organizations as an external consultant. If you would like to have my help with your team and product, feel free to contact me. 🤓

If my open source projects are useful for your product/company you can also sponsor my work on them. ☕

You can find me on:

• My website: tiangolo.com
• Twitter as @tiangolo
• GitHub as @tiangolo (you are here)
• LinkedIn
• Dev.to
• Medium

blog-posts's Issues

[Question] Consul Leader

Hello,

About post docker-swarm-mode-and-distributed-traefik-proxy-with-https/

Thank you for this post. I have a question about the Consul HA.

Since the leader is predefined in the config, what happens when the Leader crashes/its Node stops working?

Reading .env file

As far as I can tell, the .env file does not appear to be read anywhere?

Doubt about the article "React in Docker..."

This doubt is related to the article "React in Docker with Nginx, built with multi-stage Docker builds, including testing"

As you can see in the image, the generated css and js files have a hash in the file name. That is great because it allows having a very aggressive cache for that kind of files in the browser.

The problem is when you publish it as a docker service in a swarm stack and you want to update the service without downtime:

Suppose that you have multiple replicas of the same service. When you update the service, the replicas with the updated images are initiated, but the old replicas are still alive.

So, some requests will get the old HTML file (referencing the old js and css files), and some requests will get the new HTML file (referencing the new js and css files). Then when you ask for the js or css file, some replicas have it and some replicas do not.

Configure Swarm to update all the replicas at the same time mitigates the problem, but it is not useful to guarantee zero downtime.

Do you know what is the right way to deal with this?

Updates for traefik 2.0?

This article/walkthrough is awesome, and I wish Traefik documentation was as good as your articles - but I can't seem to get things running properly in Traefik 2.0 - any chance you'll be rewriting/updating this to Traefik 2.0 syntax?