Take a look at Traefik, even if you don't use containers

Post by sharperguy » Mon, May 06, 2024, 10:29 AM UTC

engine_y wrote: post #72

We've been using Traefik in prod for 2 years. While I used NGINX in the past, I decided to migrate to Traefik mainly because of the automatic let's encrypt integration. I am sorry for that decision. Traefik's documentation does not make sense to me or my team. It is finicky and misbehaves without proper logging. As an example - when I want to recreate the certificates - it fails sporadically leaving prod down for an…

  security.acme = {
    acceptTerms = true;
    defaults.email = "admin-email@provider.net";
    certs."mydomain.example.com" = {
      domain = "*.mydomain.example.com";
      dnsProvider = "cloudflare";
      environmentFile = "/path/to/cloudflare/password";
    };
  };
  
  services.caddy.enable = true;
  
  services.caddy.virtualHosts."subdomain1.mydomain.example.com" = {
    extraConfig = ''
      reverse_proxy 127.0.0.1:1234
    '';
    useACMEHost = "mydomain.example.com";
  };

Post by _lvbh » Mon, May 06, 2024, 10:59 AM UTC

sharperguy wrote: post #178

rezonant wrote: post #176

Earlier quoted context omitted.

> Technical writers: documentation by example is good only for newbies skimming through. People familiar with your product need a reference and exhaustive lists, not explanation for different fields spread over 10 tutorial pages. Well said, this extends far beyond Traefik. Far too much documentation these days is tailored for people who have never used software of it's type. This was a workable strategy during the Gr…

I've often resorted to just looking through the project on github and finding whatever source file is responsible for parsing the configuration files to figure out what each option does.

Post by boesboes » Mon, May 06, 2024, 11:07 AM UTC

engine_y wrote: post #72

We've been using Traefik in prod for 2 years. While I used NGINX in the past, I decided to migrate to Traefik mainly because of the automatic let's encrypt integration. I am sorry for that decision. Traefik's documentation does not make sense to me or my team. It is finicky and misbehaves without proper logging. As an example - when I want to recreate the certificates - it fails sporadically leaving prod down for an…

Post by bsenftner » Mon, May 06, 2024, 11:21 AM UTC

deepersprout wrote: post #68

sph wrote: post #52

Traefik is pretty cool, but suffers from the same, terrible problem of Ansible: there is a lot of documentation, and a lot of words written, yet you can never find anything you need. I have used it since v1 and I routinely get lost in their docs, and get immensely frustrated. I have been using Caddy for smaller projects simply because its documentation is not as terrible (though not great by any stretch) Technical wr…

I usually feed all the documentation to an llm and ask the question to the llm that fetches the info with rag. For example: > how do i configure Traefik to proxy traffic to two backend services? Configuring Traefik to proxy traffic to multiple backend services is a common use case. You can achieve this by defining multiple entry points and routers in Traefik's configuration, each pointing to a different backend servi…

Post by arp242 » Mon, May 06, 2024, 11:35 AM UTC

pipe01 wrote: post #182

arp242 wrote: post #115

Earlier quoted context omitted.

I never used Traefik and have no opinion on it one way or the other as such. But if this is the response to some criticism of the documentation – which you can agree or disagree with, then you've done more to turn me of from Traefik than anything anyone here can write.

Note that the commenter isn't associated with traefik itself