So far I'm loving Caddy. Super simple to configure, and the auto management of SSL certificates is magical. However, for all of the simplicity, they are still pretty resistant to properly packaging it up in the repositories. By far the longest part of getting it running, is the stupid manual configuration of launch daemons, working directories, and permissions. For software that prides itself on dead simple managemen…
>the basics of getting it into a package manager should not even be a discussion. Last time I looked into it, their problem was that Caddy plugins must be configured at compile-time, because runtime plugins seem to be hard to do with Golang (besides RPC). Because there's a handful of Caddy plugins, they'd either have to provide a slim package with no plugins, or ship with all or only some blessed plugins. Obviously a…
Caddy 0.10 Released
51–60 of 128 posts
Re: Caddy 0.10 Released
#52Does Caddy have a pluggable extension set where you can write your own middleware, in Go?
Due to the nature of the plug system, you'll have to build caddy yourself if you add customizations like that.
Re: Caddy 0.10 Released
#53Does Caddy have a pluggable extension set where you can write your own middleware, in Go?
Re: Caddy 0.10 Released
#54Re: Caddy 0.10 Released
#55How does it compare with https://traefik.io/ (reverse proxy, written in Go, automatic HTTPS / letsencrypt) ?
Re: Caddy 0.10 Released
#56I would just like to bring up how much I admire the way they want to profit off Caddy[1][2]. Sponsorships and focused development; followed by "remember, caddy is open source". My only feedback would be that they introduce a "$50/mo; my bank is not big enough" for people that wants to endorse their model/software. Look at nginx, where new functionality is hidden behind a paywall. I don't want to deny them [nginx devs…
Re: Caddy 0.10 Released
#57Anyone with experience using this as a dynamic reverse proxy - I need to proxy certain requests to private container (ports) where the port isn't known until the container is booted, and containers come up and down as users require them.
Re: Caddy 0.10 Released
#58They mention that 'Default Timeouts' have been disabled. Urging users to 'Act according to your threat model!'. I'm not sure I understand. How is not having these timeouts a security thread? Someone could potentially open up enough HTTP connections to starve others from having the opportunity to do so?
Re: Caddy 0.10 Released
#59Earlier quoted context omitted.
>the basics of getting it into a package manager should not even be a discussion. Last time I looked into it, their problem was that Caddy plugins must be configured at compile-time, because runtime plugins seem to be hard to do with Golang (besides RPC). Because there's a handful of Caddy plugins, they'd either have to provide a slim package with no plugins, or ship with all or only some blessed plugins. Obviously a…
Nginx had the same issue. Ubuntu ships 3 or 4 versions - nginx-light, nginx, nginx-full, nginx-extras - for different numbers of modules included.
Re: Caddy 0.10 Released
#60Earlier quoted context omitted.
>the basics of getting it into a package manager should not even be a discussion. Last time I looked into it, their problem was that Caddy plugins must be configured at compile-time, because runtime plugins seem to be hard to do with Golang (besides RPC). Because there's a handful of Caddy plugins, they'd either have to provide a slim package with no plugins, or ship with all or only some blessed plugins. Obviously a…
golang somewhat recently gained dynamic plugin support; wonder if that can be leveraged in Caddy? https://beta.golang.org/pkg/plugin/