4 ms·

I feel like the niche Caddy's trying to fill is for people who don't want to bother with that, or don't want to learn. If you already know how to set up nginx a

by knrz 9y ago

I feel like the niche Caddy's trying to fill is for people who don't want to bother with that, or don't want to learn. If you already know how to set up nginx and LE (like you and I do), its only appeal is relatively minor: potentially saving a quarter or half hour.

xiphias 9y ago
I think over time there will be a similar server written in Rust, where at least we can be sure that there are no buffer overflows..until then nginx is probably better in every situation.
- shawabawa3 9y ago
  Caddy is written in go, not C, so I'm not sure why it should be especially vulnerable to buffer overflows...
- ilogik 9y ago
  why would there be buffer overflows in caddy?
- Sphax 9y ago
  Do we really need someone to mention Rust in every thread ?
  - anaganisk 9y ago
    someone had to say it :p
  - afdsadf 9y ago
    As a member of the Rust Evangelism Strike Force, I am morally obligated to. /s
  - xiphias 9y ago
    No, it just makes sense to have a fast and safe HTTP server at the same time. Go is ona average 3x slower than C according to bechmarks, and it's hard to get rid of this issue because of how the language is architected. I just don't see Caddy as a possible long term replacement for nginx.
- coldtea 9y ago
  Unless it uses unsafe code (which Rust also provides) Caddy wouldn't have buffer overflows either, since Go is garbage collected and doesn't allow for the kind of pointer arithmetic C does in normal code.
- deleted 9y ago
  [deleted]
interfixus 9y ago
its only appeal is relatively minor Is that factual, or also something you feel like? To us simple folks, you know, it looks as if Caddy has a number of use cases where it's a much neater fit than nginx. We like the extreme simplicity and the transparency of it all. Some of us also like the Go it's written in. What with the magic Go modularity, you can actually embed this server in your web-app. Or is it the other way round? Comes in handy, at any rate.
- knrz 9y ago
  That was a feel. I never thought of the idea of embedding it. Thanks for teaching me more!
- grey-area 9y ago
  What with the magic Go modularity, you can actually embed this server in your web-app. Or is it the other way round? Comes in handy, at any rate. It's the other way round. You can embed your app in the server if you want to get its features for free, though given it uses net/http and most of the features are exposed there you should probably just use that directly instead if you are doing anything significant.
yjftsjthsd-h 9y ago
I'm not opposed to learning, but it's like learning emacs when nano legitimately covers all your use cases: potentially useful, but unconvincing ROI. And if we pretend for a moment that it's really only a quarter hour saved, why would I not save that time if all other things are held fixed? Caddy isn't the universal solution, but it sounds like you're rationalizing using the more complex tool because you know it and have been using it rather than because it's necessarily superior.
atonse 9y ago
The appeal is huge for a huge number of people. It's an opinionated web server. I've used nginx for probably 6-7 years, and not once have I done something I'd consider that special (I've setup fpm, passenger, gzipping of content, TLS, regenerating my DH param, etc). Every single thing I've done, could be implemented in an opinionated away by the web server. I'd love to just say "php" and have it do the right thing. In fact, I'd go as far as to say, it would be amazing if I could just say "proxy ____ drupal" instead of php, and it'll add the drupal rules as well.
overcast 9y ago
When you're a solo entrepreneur/developer/sysadmin/whateverhatineed hat I need to wear. Streamlining processes as much as possible is a good thing. Using something overly complex, just to use it, is silly. I stumbled upon Caddy, because I was struggling with getting LetsEncrypt setup properly for all my sites on Nginx. Now with a few lines of config, all my sites use, redirect to, and update their certificates automatically. One less piece of bullshit I need to sift through for all the projects I'm working on. In my opinion, something like SSL certificates SHOULD be an automated process.
andmarios 9y ago
It all depends on how complex your setup is. Caddy isn't just easy to setup, it is easy to setup every part of it until you reach the end of its functionality. I can set up both nginx and apache (and get paid for it), I've automated LE for new sites via ansible, etc. Nowadays if I can do with caddy, I just use that and proceed to the next task. Also remember that easy (and short) configuration means easier maintenance. Devs also love it, they can develop locally using advanced functionality (e.g proxying an API that doesn't provide CORS).

by knrz 9y ago

xiphias 9y ago

I think over time there will be a similar server written in Rust, where at least we can be sure that there are no buffer overflows..until then nginx is probably better in every situation.

shawabawa3 9y ago
Caddy is written in go, not C, so I'm not sure why it should be especially vulnerable to buffer overflows...
ilogik 9y ago
why would there be buffer overflows in caddy?
Sphax 9y ago
Do we really need someone to mention Rust in every thread ?
- anaganisk 9y ago
  someone had to say it :p
- afdsadf 9y ago
  As a member of the Rust Evangelism Strike Force, I am morally obligated to. /s
- xiphias 9y ago
  No, it just makes sense to have a fast and safe HTTP server at the same time. Go is ona average 3x slower than C according to bechmarks, and it's hard to get rid of this issue because of how the language is architected. I just don't see Caddy as a possible long term replacement for nginx.
coldtea 9y ago
Unless it uses unsafe code (which Rust also provides) Caddy wouldn't have buffer overflows either, since Go is garbage collected and doesn't allow for the kind of pointer arithmetic C does in normal code.
deleted 9y ago
[deleted]

interfixus 9y ago

its only appeal is relatively minor Is that factual, or also something you feel like? To us simple folks, you know, it looks as if Caddy has a number of use cases where it's a much neater fit than nginx. We like the extreme simplicity and the transparency of it all. Some of us also like the Go it's written in. What with the magic Go modularity, you can actually embed this server in your web-app. Or is it the other way round? Comes in handy, at any rate.

knrz 9y ago
That was a feel. I never thought of the idea of embedding it. Thanks for teaching me more!
grey-area 9y ago
What with the magic Go modularity, you can actually embed this server in your web-app. Or is it the other way round? Comes in handy, at any rate. It's the other way round. You can embed your app in the server if you want to get its features for free, though given it uses net/http and most of the features are exposed there you should probably just use that directly instead if you are doing anything significant.

yjftsjthsd-h 9y ago

I'm not opposed to learning, but it's like learning emacs when nano legitimately covers all your use cases: potentially useful, but unconvincing ROI. And if we pretend for a moment that it's really only a quarter hour saved, why would I not save that time if all other things are held fixed? Caddy isn't the universal solution, but it sounds like you're rationalizing using the more complex tool because you know it and have been using it rather than because it's necessarily superior.

atonse 9y ago

The appeal is huge for a huge number of people. It's an opinionated web server. I've used nginx for probably 6-7 years, and not once have I done something I'd consider that special (I've setup fpm, passenger, gzipping of content, TLS, regenerating my DH param, etc). Every single thing I've done, could be implemented in an opinionated away by the web server. I'd love to just say "php" and have it do the right thing. In fact, I'd go as far as to say, it would be amazing if I could just say "proxy ____ drupal" instead of php, and it'll add the drupal rules as well.

overcast 9y ago

When you're a solo entrepreneur/developer/sysadmin/whateverhatineed hat I need to wear. Streamlining processes as much as possible is a good thing. Using something overly complex, just to use it, is silly. I stumbled upon Caddy, because I was struggling with getting LetsEncrypt setup properly for all my sites on Nginx. Now with a few lines of config, all my sites use, redirect to, and update their certificates automatically. One less piece of bullshit I need to sift through for all the projects I'm working on. In my opinion, something like SSL certificates SHOULD be an automated process.

andmarios 9y ago

It all depends on how complex your setup is. Caddy isn't just easy to setup, it is easy to setup every part of it until you reach the end of its functionality. I can set up both nginx and apache (and get paid for it), I've automated LE for new sites via ansible, etc. Nowadays if I can do with caddy, I just use that and proceed to the next task. Also remember that easy (and short) configuration means easier maintenance. Devs also love it, they can develop locally using advanced functionality (e.g proxying an API that doesn't provide CORS).