Recently [1/2 year ago], one of Nginx's main two devs forked it into https://freenginx.org. Since then there seems to have been a flurry of activity in Nginx, especially among the official plugins.
Then, there is a also Tengine, a fork of Nginx by Taobao that is chugging along for the past ~13 years.
Long term, we have seen this happen with Mysql/Maria/Percona Server; having the fork keeps the main project open and active, but at some point I expect the fork to lose steam.
Would love to hear how someone who actually follows the DB space looks at these developments.
For a product that has both community and enterprise versions, the owner should carefully choose what kind of features should be put into the enterprise version instead of the community one, imho.
If you choose to put some basic features like analytics queries or performance improvements to your paid plan, who can trust you that the community version can still be well-supported in the future?
If only half that time was spent making better tutorials on to use and how not to use it.
Even after using a couple of 'nginx generators', reading nginx docs, stack overflow, matrix install docs..
I eventually gave up and switched to caddy, which wasn't much better - and then ended up going back to nginx and using a default someone had posted a couple years back, which appeared to be not as secure as a more advanced config would be.. but at least the matrix client worked finally.
Learned a bit on the way, including how many docs things that config should be in one place and 'modern' nginx puts it somewhere else or something.
None of the config generators' worked for my setup, and it made getting (The VERY limited) support with matrix and element a real nightmare.
Surely chatgpt can create a new nginx like system that is simple like caddy and has install / comments / docs and examples more akin to wordpress or digital ocean's (similar like kinsta's) guides - and create an expert bot to diagnose - then we can throw away all the nginx documentaion please -
now if we can make postrgrs docs better or do the same kill and remake I feel that admin life would be better.
I don't know much about caddy. I'm looking to learn more in the future. I hear many people cheering their automatic HTTPS. To me this seems like a strange reason to choose something else over nginx. I mean HTTPS is pretty much automatic in nginx if you use tools like certbot. Maybe caddy has other advantages I don't know about, but I certainly hope auto HTTPS isn't their main killer feature.
> Maybe caddy has other advantages I don't know about
Caddy's configuration format is very simple, there's far less boilerplate needed to do common things. You also don't need to do any performance tuning, as it's built using go routines, it natively uses any available resources without overloading the system.
On the topic of Automatic HTTPS, Caddy supports storage engines which make it super easy to share SSL certs on clusters.
Recently [1/2 year ago], one of Nginx's main two devs forked it into https://freenginx.org. Since then there seems to have been a flurry of activity in Nginx, especially among the official plugins.
Then, there is a also Tengine, a fork of Nginx by Taobao that is chugging along for the past ~13 years.
Long term, we have seen this happen with Mysql/Maria/Percona Server; having the fork keeps the main project open and active, but at some point I expect the fork to lose steam.
Would love to hear how someone who actually follows the DB space looks at these developments.
For a product that has both community and enterprise versions, the owner should carefully choose what kind of features should be put into the enterprise version instead of the community one, imho.
If you choose to put some basic features like analytics queries or performance improvements to your paid plan, who can trust you that the community version can still be well-supported in the future?
If only half that time was spent making better tutorials on to use and how not to use it.
Even after using a couple of 'nginx generators', reading nginx docs, stack overflow, matrix install docs..
I eventually gave up and switched to caddy, which wasn't much better - and then ended up going back to nginx and using a default someone had posted a couple years back, which appeared to be not as secure as a more advanced config would be.. but at least the matrix client worked finally.
Learned a bit on the way, including how many docs things that config should be in one place and 'modern' nginx puts it somewhere else or something.
None of the config generators' worked for my setup, and it made getting (The VERY limited) support with matrix and element a real nightmare.
Surely chatgpt can create a new nginx like system that is simple like caddy and has install / comments / docs and examples more akin to wordpress or digital ocean's (similar like kinsta's) guides - and create an expert bot to diagnose - then we can throw away all the nginx documentaion please -
now if we can make postrgrs docs better or do the same kill and remake I feel that admin life would be better.
I don't get it, this is just their github repo? Am I missing something or were there some news I'm out of the loop of?
I was so happy to use Nginx after Apache. I am equally happy now to use Caddy.
Apache 2 isn't bad, to my mind.
But Caddy does so much more out of the box. (Sometimes you need and enjoy it, sometimes you'd rather have a simpler tool.)
It’s the automatic https that gets you in.
I don't know much about caddy. I'm looking to learn more in the future. I hear many people cheering their automatic HTTPS. To me this seems like a strange reason to choose something else over nginx. I mean HTTPS is pretty much automatic in nginx if you use tools like certbot. Maybe caddy has other advantages I don't know about, but I certainly hope auto HTTPS isn't their main killer feature.
> Maybe caddy has other advantages I don't know about
Caddy's configuration format is very simple, there's far less boilerplate needed to do common things. You also don't need to do any performance tuning, as it's built using go routines, it natively uses any available resources without overloading the system.
On the topic of Automatic HTTPS, Caddy supports storage engines which make it super easy to share SSL certs on clusters.
Someone's part of the lucky 10,000
https://xkcd.com/1053/
At least they're not deploying another IIS server somewhere on the Internet.