4 ms·

I started using caddy v1 thanks to lightning-fast and simple TLS setup and extremely simple configuration in general, thanks to the excellent docs and handy plu

I started using caddy v1 thanks to lightning-fast and simple TLS setup and extremely simple configuration in general, thanks to the excellent docs and handy plugins for common stuff like cors, rewrites and fastcgi. Shortly after upgrading to caddy v2, I switched to nginx, after spending way too much time trying to make sense of the new Caddyfile and docs (the thing I miss the most of the docs is the plugin list, along with the cors plugin, and in general the non-existant entry curve of Caddy v1). Tbh, I also miss the one-liner install script <3 I'm genuinely sorry for the project; I didn't mind at all any of the previous so-called shady behavior (I personally don't object at all against a developer trying to make a living out of his own open-source project); I've been using caddy for four years now, and I really hope to switch back to it, one day. Thank you for your work, mholt! <3

francislavoie 6y ago
If you need any help when coming back to Caddy v2, come ask for help on the community forums: https://caddy.community/ https://caddy.community/ We'll be glad to help you get set up! The docs are still a work in progress, we'll eventually have a plugin registry like in v1 but that requires a bunch of work behind the scenes to make it happen.
mholt 6y ago
As francislavoie said, the website with its nice one-click custom download page and list of registered plugins is a lot of work. It'll come, but it's not ready yet. Much like the v1 release 5 years ago where the interactive download page didn't come until about a year later, it'll take some time. Hopefully not a full year though. :) I've already got the new build server mostly written -- should be way faster.
- coder543 6y ago
  Maybe this has changed since I looked at things yesterday, but I couldn't find a list of default plugins anywhere on the website, nor how to configure those default plugins. I think this is what the person you're replying to is talking about. On the old site, there was a plugin documentation page that made it trivial to see what the plugins were called and what options they took. I eventually asked my local copy of Caddy what plugins were available, which answered one of the two questions, but am I missing some kind of documentation page? The interactive, custom build page is an unrelated, but also interesting topic. About a year ago, I was using abiosoft's Caddy Builder image to build a Caddy docker image with the plugins I wanted, but this no longer seems to work even for Caddy V1, and I don't think it has been updated for V2. It would be awesome if there were an official Caddy Builder docker image. Even if the website existed, I would still have to wrap that binary in a docker image somehow for my own use cases. But, these are all just my personal opinions -- I'm sure you have your own priorities for the project, and I'm excited to see V2 has officially released!
  - hairyhenderson 6y ago
    > It would be awesome if there were an official Caddy Builder docker image You're in luck! :D https://hub.docker.com/_/caddy https://hub.docker.com/_/caddy Note that the v2 images were _just_ pushed a few minutes ago, so the description might still point to rc3. See "Adding custom Caddy modules" on that page for instructions on how to use the `caddy:builder` image.
  - mholt 6y ago
    The new website does not yet have the ability to register plugins. I'm writing it -- I already have the new build server mostly written -- but like with v1, it may take a few months. It's not worth delaying the release for that, especially when we have tools like xcaddy that make it easy to build Caddy with plugins, no need to touch any code: https://github.com/caddyserver/xcaddy https://github.com/caddyserver/xcaddy Right now, the process is: find a plugin you like, then run: xcaddy build --with <module-path> But yeah, it will get easier with time. We'll get there.
  - m_sahaf 6y ago
    The list of core plugins (now called modules) is here: https://caddyserver.com/docs/modules/ https://caddyserver.com/docs/modules/ If you're navigating from the homepage, click on "Documentation" at the top, then click on "modules" on the left navbar just above "JSON Config Structure". That list is generated directly from the source code, so it is the definite list of what's included by default and supported by the native JSON config. The other way is, as you found out, to run `caddy list-modules` to get the definitive list of what's packed into the binary.
    - coder543 6y ago
      Thanks, this is what I was looking for!

francislavoie 6y ago

If you need any help when coming back to Caddy v2, come ask for help on the community forums: https://caddy.community/ https://caddy.community/ We'll be glad to help you get set up! The docs are still a work in progress, we'll eventually have a plugin registry like in v1 but that requires a bunch of work behind the scenes to make it happen.

mholt 6y ago

As francislavoie said, the website with its nice one-click custom download page and list of registered plugins is a lot of work. It'll come, but it's not ready yet. Much like the v1 release 5 years ago where the interactive download page didn't come until about a year later, it'll take some time. Hopefully not a full year though. :) I've already got the new build server mostly written -- should be way faster.

coder543 6y ago
Maybe this has changed since I looked at things yesterday, but I couldn't find a list of default plugins anywhere on the website, nor how to configure those default plugins. I think this is what the person you're replying to is talking about. On the old site, there was a plugin documentation page that made it trivial to see what the plugins were called and what options they took. I eventually asked my local copy of Caddy what plugins were available, which answered one of the two questions, but am I missing some kind of documentation page? The interactive, custom build page is an unrelated, but also interesting topic. About a year ago, I was using abiosoft's Caddy Builder image to build a Caddy docker image with the plugins I wanted, but this no longer seems to work even for Caddy V1, and I don't think it has been updated for V2. It would be awesome if there were an official Caddy Builder docker image. Even if the website existed, I would still have to wrap that binary in a docker image somehow for my own use cases. But, these are all just my personal opinions -- I'm sure you have your own priorities for the project, and I'm excited to see V2 has officially released!
- hairyhenderson 6y ago
  > It would be awesome if there were an official Caddy Builder docker image You're in luck! :D https://hub.docker.com/_/caddy https://hub.docker.com/_/caddy Note that the v2 images were _just_ pushed a few minutes ago, so the description might still point to rc3. See "Adding custom Caddy modules" on that page for instructions on how to use the `caddy:builder` image.
- mholt 6y ago
  The new website does not yet have the ability to register plugins. I'm writing it -- I already have the new build server mostly written -- but like with v1, it may take a few months. It's not worth delaying the release for that, especially when we have tools like xcaddy that make it easy to build Caddy with plugins, no need to touch any code: https://github.com/caddyserver/xcaddy https://github.com/caddyserver/xcaddy Right now, the process is: find a plugin you like, then run: xcaddy build --with <module-path> But yeah, it will get easier with time. We'll get there.
- m_sahaf 6y ago
  The list of core plugins (now called modules) is here: https://caddyserver.com/docs/modules/ https://caddyserver.com/docs/modules/ If you're navigating from the homepage, click on "Documentation" at the top, then click on "modules" on the left navbar just above "JSON Config Structure". That list is generated directly from the source code, so it is the definite list of what's included by default and supported by the native JSON config. The other way is, as you found out, to run `caddy list-modules` to get the definitive list of what's packed into the binary.
  - coder543 6y ago
    Thanks, this is what I was looking for!