3 ms·

I wouldn't put effort into changing if you have no troubles with nginx. Caddy has some neat features like live-configuration and built in LetsEncrypt. Plus the

by evv 4y ago

I wouldn't put effort into changing if you have no troubles with nginx. Caddy has some neat features like live-configuration and built in LetsEncrypt. Plus the JSON configuration is a great idea, once I get it working. The real reason is the thing you highlighted: "I can see there are some NGINX Plus features that are free in Caddy." Sadly it seems that NGINX is now crippleware. Personally I find it risky to depend on open source organizations who refuse to accept important features to the project, so they can sell those features as proprietary.

number6 4y ago
Back in the days, there was an issue with caddy regarding having to pay for it if you bundle some plugins with it. I can't remember now - must have been years ago. This is why I ultimately landed at traefik and nginx as my go-to setup. Is this still the case?
- francislavoie 4y ago
  No. See https://github.com/caddyserver/caddy/issues/2786 https://github.com/caddyserver/caddy/issues/2786 And to be clear, only builds produced by the official Caddy website used to be commercially licensed (not anymore). But the code has always been open source, and you could always build from source for free for commercial use.
  - number6 4y ago
    Thanks for the clarification! So they changed it 3 years ago. I will definitely consider it in future projects. > But the code has always been open source, and you could always build from source for free for commercial use. Back in the days there were some workaround projects that build for you. Well caddy was relatively new then so I abandoned it for my projects.
sgt 4y ago
You could also see it another way - nginx has to make money to fund further development. By taking features that are not critical to 90% of users, and making them paid features, you help ensure the longevity of the project. This could be a good thing.

by evv 4y ago

number6 4y ago

Back in the days, there was an issue with caddy regarding having to pay for it if you bundle some plugins with it. I can't remember now - must have been years ago. This is why I ultimately landed at traefik and nginx as my go-to setup. Is this still the case?

francislavoie 4y ago
No. See https://github.com/caddyserver/caddy/issues/2786 https://github.com/caddyserver/caddy/issues/2786 And to be clear, only builds produced by the official Caddy website used to be commercially licensed (not anymore). But the code has always been open source, and you could always build from source for free for commercial use.
- number6 4y ago
  Thanks for the clarification! So they changed it 3 years ago. I will definitely consider it in future projects. > But the code has always been open source, and you could always build from source for free for commercial use. Back in the days there were some workaround projects that build for you. Well caddy was relatively new then so I abandoned it for my projects.

sgt 4y ago

You could also see it another way - nginx has to make money to fund further development. By taking features that are not critical to 90% of users, and making them paid features, you help ensure the longevity of the project. This could be a good thing.