top | item 21154893

Caddy Proposal: Permanently change all proprietary licensing to open source

357 points| scrollaway | 6 years ago |github.com | reply

76 comments

order
[+] djsumdog|6 years ago|reply
It's been a while since I've seen Caddy here and I do remember all the controversy over the licensing. It is difficult to make an open source project and find a way to monetize/live off of it and there's always been that push/pull with projects like this, Redis, and others.

Back during that mess, I settled on haproxy+certbot+nginx in containers to setup my personal sites, but something like Caddy can greatly simplify that kind of stack.

This is pretty cool news and I hope this project continues to develop. How have they solved their funding problems? Does this have to do with the comment about Ardan Labs? For other people with FOSS projects who want to be able to work on this kind of stuff full time and not care about motorization, what options are there (other than Patreon/crowd/community type funding?)

[+] dullgiulio|6 years ago|reply
Nginx does have paid-only features, so I don't really think your "purity move" hit the target...

The harsh truth is that even Free Software costs money to write, and developers should be paid.

[+] M4v3R|6 years ago|reply
They said that they will focus on supporting enterprise clients, so that’s probably where the money will come from. This is similar to what Nginx is doing I believe.
[+] paulddraper|6 years ago|reply
From Github

> Congratulations! Interesting new approach to funding open source: get acquired and let them figure it out!

[+] de_watcher|6 years ago|reply
Oh, I thought it's a proposal to permanently change all proprietary licensing in the world to open source...
[+] instagraham|6 years ago|reply
Yeah, me too. I actually thought of it as a sort of innovation-economic stimulus package and went "oh wow, this could work".

Imagine the amount of innovation we'd get if this happened with hardware too.

But then I opened the article and was brought back to earth. soon

[+] atonse|6 years ago|reply
My guess is they’re doing this since maybe Caddy’s growth may have slowed down since they did that confusing commercial use licensing?

I went from “I’m going to use this everywhere” to “I’ll switch back to nginx the next time I have time to transition back” Because it was too expensive to host little sites on. I’m relieved that I procrastinated. Now i can continue to use it in many places since Caddy is awesome.

[+] joncalhoun|6 years ago|reply
My guess is you are incorrect and this has more to do with the Ardan Labs partnership[1][2]. This release also came shortly after Bill (founder of Ardan Labs) went to visit Matt and discuss Caddy[3], which helps support that claim.

Prior to the partnership I believe the real issue was that Matt & co didn't have a sustainable way to maintain the project and they were trying to figure that out. I don't know the details of the partnership with Ardan Labs, but my guess is it is structured in a way that allows Caddy to focus solely on building out a great product without worrying about monetizing it so they dropped all the proprietary licensing.

[1] - https://www.ardanlabs.com/news/2019/05/ardan-labs-partners-w... [2] - https://twitter.com/mholt6/status/1179957356005707776 [3] - https://twitter.com/goinggodotnet/status/1178949305421438976

[+] therein|6 years ago|reply
As long as the author can keep his hands from injecting "Sponsored-By" headers into my responses, I'd call it a win.
[+] herohamp|6 years ago|reply
I would happily accept sponsored by headers if it meant free commercial use of caddy
[+] pjmlp|6 years ago|reply
Depends, are you willing to actually pay in some form for using it?

Donations, books, patreon, pull requests.

[+] coleca|6 years ago|reply
This is great news for Caddy. I have worked with Ardan Labs in the past and they are a terrific organization with some incredibly talented engineers.
[+] kemitchell|6 years ago|reply
I have done only a smidgen of Go programming, and don't know Caddy or any of the firms mentioned in the issue.

Do I correctly understand that Light Code Labs, the company steward of the Caddy project, is shifting to an entirely professional services-based business model, which is Ardan Labs' business model, by partnering with them?

[+] mrunkel|6 years ago|reply
What I understood was that in the future Ardan Labs would provide paid support for Caddy. Light Code Labs would receive financial support directly from Ardan Labs.

Since Ardan Labs is already in the support business, this would allow them to expand their business while Light Code could focus on coding.

[+] IshKebab|6 years ago|reply
This is great news, I hope it works out for them. Caddy is definitely the easiest web server to set up, and it was a shame when it went commercial, even though I probably would have done the same thing.
[+] Calashle0202|6 years ago|reply
Never heard of the project, but looks good. Good to see they are making efforts to change the license.

Curious, who/when would you use caddy? If I were to be building and deploying microservices with the likes of Gin, Mux, etc.. would I have a use for this library? Or is this primarily for those wanting to serve static html pages? Still trying to get a foot hold on what my tool kit is going to consist of to build my software product.

[+] scrollaway|6 years ago|reply
I've used caddy in places where I needed nginx but wanted end to end ssl and didn't want to deal with local letsencrypt cronjobs.

But caddy is also pretty cool to use as a development web server as well.

[+] corobo|6 years ago|reply
I’m planning on using Caddy to provide bring-your-own-domain handling for a project I’m working on. Your user points their domain to your caddy server and it sets up https automatically - including the certificate - during the first request

https://caddyserver.com/docs/automatic-https#on-demand

Obviously not what it’s limited to, but that’s it’s selling feature for me

[+] manigandham|6 years ago|reply
Caddy is a webserver and can be used for static or dynamic sites in any stack. It's primary popular feature was easy and automatic SSL via LetsEncrypt integration.

You can look at the features list to see more: https://caddyserver.com/features

[+] bovermyer|6 years ago|reply
I use Caddy (the compiled product) as the reverse proxy and automagic SSL certificate manager for all of my personal sites.

I do not use Caddy (the code) as a library.