4 ms·

I don't understand the change. If I understand the history correctly, previously commercial usage restrictions only applied to official binaries downloaded from

by jack12 7y ago

I don't understand the change. If I understand the history correctly, previously commercial usage restrictions only applied to official binaries downloaded from their site, and now: >Going forward, only commercial use of ... the download page ... requires a subscription So now you're allowed to commercially use the official binaries without buying a license, but you're not allowed to acquire them without that license? I don't really understand how that's a distinction with any difference. Is the expectation that (non-commercial) 3rd-parties will mirror the official binaries, and that's why it's a useful change?

TAForObvReasons 7y ago
> Now that version 1.0 is tagged, we will see about working on integrations with Digital Ocean, various Linux distros and package managers, and making an official Docker container. So it seems that if you use the Docker container or an APT repository, there is no need for a subscription. However if you pull from their infrastructure you need to pay. Interesting way to muddy the waters and extract money from those who don't understand the situation.
- mholt 7y ago
  That's not correct. To clarify the facts: - You can always build from source, and you could have always built from source, for free, for commercial use, since the source code is and has always been Apache licensed. - 3rd-party distribution channels such as Digital Ocean images, Linux package managers, Docker, etc, have nothing to do with commercial or free use. - Using our official download page (or getcaddy.com) for commercial purposes requires a subscription.
  - TAForObvReasons 7y ago
    The Caddy source code is hosted on GitHub, not on your infrastructure AFAICT. If that changed, then what you wrote is different from what I wrote. Otherwise, nothing written in the previous comment differs from what you just wrote.
    - mholt 7y ago
      Your comment does not qualify "need to pay", which is only required for commercial users. If Caddy is as unpopular as HN makes it look, then that's probably nobody. Right?
      - TAForObvReasons 7y ago
        Just to be clear: it seems that the same exact binaries distributed via a docker image or through standard distro packages managers are free for commercial use. The difference is that obtaining it from you directly costs money. This is a part of the business model that HN users would likely find distasteful. You're charging people who aren't technically competent enough to realize that other places offer the same exact binaries for free. Why even permit the side channels in the first place?
        mholt 7y ago
        That's also an incorrect characterization. Those 3rd-party channels do not give you the power to customize Caddy the way our build infrastructure does. Try customizing Caddy with plugins through apt or DO images and let us know if you find a way to do that!
        gtirloni 7y ago
        I understand other projects have similar compilation requirements but now you're just spinning a technical difficulty as a feature. The fact people are still having trouble understanding your licensing terms should give you pause.

by jack12 7y ago

TAForObvReasons 7y ago

> Now that version 1.0 is tagged, we will see about working on integrations with Digital Ocean, various Linux distros and package managers, and making an official Docker container. So it seems that if you use the Docker container or an APT repository, there is no need for a subscription. However if you pull from their infrastructure you need to pay. Interesting way to muddy the waters and extract money from those who don't understand the situation.

mholt 7y ago
That's not correct. To clarify the facts: - You can always build from source, and you could have always built from source, for free, for commercial use, since the source code is and has always been Apache licensed. - 3rd-party distribution channels such as Digital Ocean images, Linux package managers, Docker, etc, have nothing to do with commercial or free use. - Using our official download page (or getcaddy.com) for commercial purposes requires a subscription.
- TAForObvReasons 7y ago
  The Caddy source code is hosted on GitHub, not on your infrastructure AFAICT. If that changed, then what you wrote is different from what I wrote. Otherwise, nothing written in the previous comment differs from what you just wrote.
  - mholt 7y ago
    Your comment does not qualify "need to pay", which is only required for commercial users. If Caddy is as unpopular as HN makes it look, then that's probably nobody. Right?
    - TAForObvReasons 7y ago
      Just to be clear: it seems that the same exact binaries distributed via a docker image or through standard distro packages managers are free for commercial use. The difference is that obtaining it from you directly costs money. This is a part of the business model that HN users would likely find distasteful. You're charging people who aren't technically competent enough to realize that other places offer the same exact binaries for free. Why even permit the side channels in the first place?
      - mholt 7y ago
        That's also an incorrect characterization. Those 3rd-party channels do not give you the power to customize Caddy the way our build infrastructure does. Try customizing Caddy with plugins through apt or DO images and let us know if you find a way to do that!
        gtirloni 7y ago
        I understand other projects have similar compilation requirements but now you're just spinning a technical difficulty as a feature. The fact people are still having trouble understanding your licensing terms should give you pause.