Announcing Caddy Commercial Licenses
caddyserver.com
Announcing Caddy Commercial Licenses
1–10 of 295 posts
Re: Announcing Caddy Commercial Licenses
#2Beginning today, all official Caddy binaries come with an End User License Agreement (EULA) that designates them either for Personal (non-commercial) or Commercial use. To be clear, this EULA applies only to Caddy binaries you download; it does not apply to the source code. Caddy is still open source, and the source code is under the same Apache 2.0 license.
Thanks for keeping it open source. I'm very interested in how this business model will work, glad to see people trying different approaches.
Re: Announcing Caddy Commercial Licenses
#3> 1/4 price of comparable servers
Which servers?
Re: Announcing Caddy Commercial Licenses
#4Key Quote: To be clear, this EULA applies only to Caddy binaries you download; it does not apply to the source code. Caddy is still open source, and the source code is under the same Apache 2.0 license.
Doesn't this mean that you can simply compile Caddy from source, and avoid having to pay for commercial use? Most Caddy users are likely going be comfortable with compiling stuff, so what benefits does paying bring besides private plugin hosting?
Re: Announcing Caddy Commercial Licenses
#5
Re: Announcing Caddy Commercial Licenses
#6I always find it funny when the announcement of a new, pay for software, especially a web server leads to 503. Especially when it looks like an HTML page.
Re: Announcing Caddy Commercial Licenses
#7> If you use Caddy for personal, academic, or non-profit purposes, not much is different. Caddy-Sponsors HTTP Header
> If you use or distribute official Caddy binaries at work, or as part of a product/service, you will need a commercial license
If I have some personal project which I want to incorporate I need to worry about the license.
Oh, time to switch back to NGINX. Thanks for automated HTTPS while it lasted.
Re: Announcing Caddy Commercial Licenses
#8Key Quote: To be clear, this EULA applies only to Caddy binaries you download; it does not apply to the source code. Caddy is still open source, and the source code is under the same Apache 2.0 license. Doesn't this mean that you can simply compile Caddy from source, and avoid having to pay for commercial use? Most Caddy users are likely going be comfortable with compiling stuff, so what benefits does paying bring be…
That's often the case. The answer is priority support and developer time for bugfixes/feature requests, and potentially commercial-only features.
Think Red Hat Linux.
Re: Announcing Caddy Commercial Licenses
#9homepage 503 https://dl.dropboxusercontent.com/s/phh5xebd1jqj27l/2017-09-...
Ugh, I forgot to raise the file descriptor limit when I re-provisioned the site. Leave it to me to blunder that. :)
Re: Announcing Caddy Commercial Licenses
#10Key Quote: To be clear, this EULA applies only to Caddy binaries you download; it does not apply to the source code. Caddy is still open source, and the source code is under the same Apache 2.0 license. Doesn't this mean that you can simply compile Caddy from source, and avoid having to pay for commercial use? Most Caddy users are likely going be comfortable with compiling stuff, so what benefits does paying bring be…
AFAIK you have to specify plugins at compile time in the source code. Don't know if the installation scripts/endpoints that spit out the official binaries are open source, though.