bmarinov

I use Traefik because it solved a problem with the static configuration approach which Nginx had / still has.

In a scenario with multiple services behind Nginx, taking one down or replacing an instance is massive headache. I tried to script around it, but basically the Nginx container would choke on the fact that a service does not [yet / anymore] exist, and together with the docker networking stack it turned out to be an insurmountable problem.

Traefik otoh discovers services based on (in my case) labels on the docker containers running locally. And then updates the configuration on the fly.

Basically the static approach to configuration resulted in massive headache when I needed to enable zero downtime deployments and updates behind Nginx. And Traefik handled it perfectly without dropping a single request.

Nowadays I manage my dynamic configuration with ansible and update the values in for the file-based configuration provider with a playbook. I don't need a UI to manage my inventory, I use ansible for that. Traefik handles the rest perfectly.

Traefik does auto discovery and you can register different configuration providers. Don't need docker? Then don't use the docker label-based provider. It is really flexible and has sensible defaults. Other than a few quirks in the basic auth support I haven't had any problems. And at work it powers our globally utilized infrastructure without any hiccups.

Ich glaube, dass das im besten Fall sehr unwahrscheinlich ist, ich würde es als komplett unrealistisch bezeichnen. Dass Fliegen irgendwann nicht mehr erwünscht oder begehrt wird.

Die Zeit ist immer ein Faktor, und wenn Urlaubstage begrenzt sind, will man möglichst schnell ans Ziel kommen. Dasselbe gilt für die Arbeit, wenn ich für einen Meeting vor Ort sein muss, und quer durch Europa (oder weiter weg) reisen, gibt es keine Alternativen.

Ich kann der Wunsch vollkommen nachvollziehen, und ich begrüße jede Maßnahme für Reduktion unnötiger Flüge. Sprich - die klassischen Berater- innendeutsche Flüge, Massentourismus usw. Aber in eine globalisierte Welt wird es fliegen geben müssen. Viele Leute wohnen weit weg von der Familie. Mit unsere kleine Tochter können wir zb nicht einfach so 12+ Stunden am Stück reisen, um meine Eltern zu besuchen. Nur so als einen Beispiel.

It's not the cooling, according to GN also server SKUs running on stock have massive failure rates. Check out their recent video. Here is a link :) https://www.youtube.com/watch?v=oAE4NWoyMZk

I'm also using ansible everywhere in my home / private infra and lab. Occasionally I get slightly annoyed that I have to open an inventory file or a role var to find something. But in general I'm so grateful that there is one place to find this information, and the same is used to set up everything from scratch.

Is it extra work to write the roles and playbooks? Yes. Does it solve the documentation and automation problem completely? Absolutely. 10/10 would recommend. And for the record, most things I host run on containers, but the volumes and permission management alone make it worth your time.

Too late for that

Storage is not easy when you don't have massive amounts of free land. This is an ongoing debate in Europe, and in one particular country a leaky storage was discovered just a month or two ago. Again.

And there is no guarantee that what we build today is not going to be a massive liability in 50 or 200 or hell, 500 years. But the companies and people who are responsible will not even exist at this point.

What about the storage for the used fuel? This is a massive problem for any country not occupying half a continent.

Man könne auch eine gewisse Zeit crossposten, und darauf hinweisen. Ich fände es super, ein paar communities auf den Server mit content zu versorgen. Diese dann zu folgen = mehr Traffik auf die neue Communities.

Das ist aber für den Arbeitgeber nicht egal, und es hat Einfluss auf das Gehalt, der sich die Firma überhaupt leisten kann.

You would be better off with a dongle. I have one which supports hi-res audio and has plenty of power to drive my over ear audionerd headphones. Phone jacks and DACs can't ever match that.

It is one of the easier ways to globally configure git auth for private Go packages.