6 ms·

It's open source, right? Just compile it yourself? To your lager point, I think paying for software is and has been the norm in many places. So nothing new.

shubhamjain 8y ago
I didn't notice that you can compile the source code yourself to avoid paying for the license. That seems to be a nice alternative.
- mfontani 8y ago
  Only if you're not using it for commercial stuff. If you're using it for commercial stuff you have to pay the $25/month
  - pfg 8y ago
    The code is released under the Apache License. You're free to compile the source code and use it commercially. You're not allowed to do that with the official binaries.
  - wccrawford 8y ago
    My understanding of their license page is different. "If your company uses official Caddy binaries internally, in production, or distributes Caddy, a commercial license is required." "If I build Caddy from source, which license applies?" "The source code is Apache 2.0 licensed." https://caddyserver.com/products/licenses https://caddyserver.com/products/licenses
    - jstanley 8y ago
      Would be interested to see how reproducible builds would interact in such a situation. I.e. you get a byte-identical binary file if you build it yourself, but you don't have to pay the $25/mo. Even though you end up at exactly the same place. Something like http://ansuz.sooke.bc.ca/entry/23 http://ansuz.sooke.bc.ca/entry/23 "What colour are your bits?" I suppose.
romanovcode 8y ago
> It's open source, right? Just compile it yourself? The point was that it was easy to install and get it running. Your point defeats the purpose of Caddy in the first place. It would be much easier to: 1. `sudo apt-get install nginx-extras python-certbot-nginx` 2. Add simple config with 80 port of your website/reverse proxy. 3. `sudo certbot --nginx` 4. Do not worry that you will be sued by nginx for using it for commercial purposes.
- codetrotter 8y ago
  Installing Caddy is easy. https://github.com/mholt/caddy#build https://github.com/mholt/caddy#build Init scripts are included as well, both for FreeBSD, macOS and for a several different init systems used by various Linux distros. https://github.com/mholt/caddy/tree/master/dist/init https://github.com/mholt/caddy/tree/master/dist/init FreeBSD even has it in the ports collection, so you can install it using the package manager that is included with FreeBSD doas pkg install caddy Once installed on FreeBSD with the above command, create a configuration file in the Caddyfile format in /usr/local/www/Caddyfile. Example Caddyfile: www.mysite.com { root /var/www/com.mysite.www } mysite.com { redir https://www.mysite.com{uri} } sub.mysite.com { root /var/www/com.mysite.sub gzip log /var/log/com.mysite.sub/access.log } Provide an SSL certificate issuer email in your rc.conf. By providing an email address you automatically agree to letsencrypt.org's general terms and conditions: doas sysrc caddy_cert_email="your.email@example.org" Enable caddy in your rc.conf: doas sysrc caddy_enable="YES" Start the server: doas service caddy start > Do not worry that you will be sued by nginx for using it for commercial purposes. The source code of Caddy is distributed under the terms of the Apache 2.0 license. https://github.com/mholt/caddy/blob/master/LICENSE.txt https://github.com/mholt/caddy/blob/master/LICENSE.txt
  - st3fan 8y ago
    (Maybe I should switch to FreeBSD?) Wait I have to manually install Caddy and then fight with systemd to make it start at boot? What is this? The 90? Since they don't have have a standard package repo, you will also always be behind. You will have to keep track of their releases manually to make sure you are not missing an important update. It is unclear why these folks have are resisting standard packages. Is that incompatible with their business model? It made me move away from Caddy and instead go with Nginx and Certbot. Which is simpler and less maintenance work in the long run.

shubhamjain 8y ago

I didn't notice that you can compile the source code yourself to avoid paying for the license. That seems to be a nice alternative.

mfontani 8y ago
Only if you're not using it for commercial stuff. If you're using it for commercial stuff you have to pay the $25/month
- pfg 8y ago
  The code is released under the Apache License. You're free to compile the source code and use it commercially. You're not allowed to do that with the official binaries.
- wccrawford 8y ago
  My understanding of their license page is different. "If your company uses official Caddy binaries internally, in production, or distributes Caddy, a commercial license is required." "If I build Caddy from source, which license applies?" "The source code is Apache 2.0 licensed." https://caddyserver.com/products/licenses https://caddyserver.com/products/licenses
  - jstanley 8y ago
    Would be interested to see how reproducible builds would interact in such a situation. I.e. you get a byte-identical binary file if you build it yourself, but you don't have to pay the $25/mo. Even though you end up at exactly the same place. Something like http://ansuz.sooke.bc.ca/entry/23 http://ansuz.sooke.bc.ca/entry/23 "What colour are your bits?" I suppose.

romanovcode 8y ago

> It's open source, right? Just compile it yourself? The point was that it was easy to install and get it running. Your point defeats the purpose of Caddy in the first place. It would be much easier to: 1. `sudo apt-get install nginx-extras python-certbot-nginx` 2. Add simple config with 80 port of your website/reverse proxy. 3. `sudo certbot --nginx` 4. Do not worry that you will be sued by nginx for using it for commercial purposes.

codetrotter 8y ago
Installing Caddy is easy. https://github.com/mholt/caddy#build https://github.com/mholt/caddy#build Init scripts are included as well, both for FreeBSD, macOS and for a several different init systems used by various Linux distros. https://github.com/mholt/caddy/tree/master/dist/init https://github.com/mholt/caddy/tree/master/dist/init FreeBSD even has it in the ports collection, so you can install it using the package manager that is included with FreeBSD doas pkg install caddy Once installed on FreeBSD with the above command, create a configuration file in the Caddyfile format in /usr/local/www/Caddyfile. Example Caddyfile: www.mysite.com { root /var/www/com.mysite.www } mysite.com { redir https://www.mysite.com{uri} } sub.mysite.com { root /var/www/com.mysite.sub gzip log /var/log/com.mysite.sub/access.log } Provide an SSL certificate issuer email in your rc.conf. By providing an email address you automatically agree to letsencrypt.org's general terms and conditions: doas sysrc caddy_cert_email="your.email@example.org" Enable caddy in your rc.conf: doas sysrc caddy_enable="YES" Start the server: doas service caddy start > Do not worry that you will be sued by nginx for using it for commercial purposes. The source code of Caddy is distributed under the terms of the Apache 2.0 license. https://github.com/mholt/caddy/blob/master/LICENSE.txt https://github.com/mholt/caddy/blob/master/LICENSE.txt
- st3fan 8y ago
  (Maybe I should switch to FreeBSD?) Wait I have to manually install Caddy and then fight with systemd to make it start at boot? What is this? The 90? Since they don't have have a standard package repo, you will also always be behind. You will have to keep track of their releases manually to make sure you are not missing an important update. It is unclear why these folks have are resisting standard packages. Is that incompatible with their business model? It made me move away from Caddy and instead go with Nginx and Certbot. Which is simpler and less maintenance work in the long run.