4 ms·

I really like how it can be easily configured from Docker labels (from Portainer for example), or from your big production Consul cluster alike. But yeah, the d

I really like how it can be easily configured from Docker labels (from Portainer for example), or from your big production Consul cluster alike. But yeah, the docs need a lot of work, it’s difficult to figure out the format many times, it lacks examples, and things that need to be enabled together have their docs at different places.

baby_souffle 1y ago
Your point about having to enable two different things at the same time in two different places is a concise way of expressing my extreme frustration with that project. I burned the better part of a Saturday trying to figure out why a relatively straightforward configuration wasn't applying and it's because one half of the configuration that I was trying to apply has to be done in the static manner and not the dynamic manner. Documentation doesn't really spell this out and after quite a bit of frustrated googling I found a few other people complaining about effectively the same problem. It's only a few lines of code to spit out something along the lines of "hey, you're trying to configure ¢thing in an inappropriate way. Did you mean to configure ¢thing over in €thisLocation?" message... But nope, that would make things so much simpler and easier to use and probably cut into their support contract sales... Now I basically just stick with nginx because it's documentation isn't crap, useful and applicable examples are all over the Internet.
- mkesper 1y ago
  Sticking to nginx seems not to be an option for many as at least ingress-nginx will not be get any new features anymore (as mentioned in the article).
  - baby_souffle 1y ago
    > Sticking to nginx seems not to be an option for many as at least ingress-nginx will not be get any new features anymore (as mentioned in the article). For k8s, yeah. It should still be a useful tool for other things? Or did i miss a memo about nginx being EOLd?

baby_souffle 1y ago

Your point about having to enable two different things at the same time in two different places is a concise way of expressing my extreme frustration with that project. I burned the better part of a Saturday trying to figure out why a relatively straightforward configuration wasn't applying and it's because one half of the configuration that I was trying to apply has to be done in the static manner and not the dynamic manner. Documentation doesn't really spell this out and after quite a bit of frustrated googling I found a few other people complaining about effectively the same problem. It's only a few lines of code to spit out something along the lines of "hey, you're trying to configure ¢thing in an inappropriate way. Did you mean to configure ¢thing over in €thisLocation?" message... But nope, that would make things so much simpler and easier to use and probably cut into their support contract sales... Now I basically just stick with nginx because it's documentation isn't crap, useful and applicable examples are all over the Internet.

mkesper 1y ago
Sticking to nginx seems not to be an option for many as at least ingress-nginx will not be get any new features anymore (as mentioned in the article).
- baby_souffle 1y ago
  > Sticking to nginx seems not to be an option for many as at least ingress-nginx will not be get any new features anymore (as mentioned in the article). For k8s, yeah. It should still be a useful tool for other things? Or did i miss a memo about nginx being EOLd?