News for hackers. Stuff that matters.

A comment on Announcing Caddy Commercial Licenses. Parent comment

Re:Announcing Caddy Commercial Licenses by JosephLark on Wednesday September 13, 2017 @10:30AM (#15238611)
> No. The point is, you've annoyed someone who liked your software, used it for personal use (costing you nothing) and would've happily recommended it to colleagues.

This is worth keeping in mind. Personally, this change is putting me off Caddy to the point that I might stop using it for personal sites. The big feature for me - instant LetsEncrypt TLS certificates - can be done on other servers now fairly simply. So the end result might be that I no longer use Caddy, which means I'll no longer have it in mind for commercial projects I work on.

[ Parent | on HN ]
Re:Announcing Caddy Commercial Licenses by djsumdog on Wednesday September 13, 2017 @10:41AM (#15238717)
I have pretty much the same reaction. I was considering moving some stuff to Caddy, but looking at this, I'd need to create my own build pipeline to keep rubbish like this out. No thanks. I'll use tools that give me the options of turning things like this on/off without having to compile my own copy.
[ Parent | on HN ]
Re:Announcing Caddy Commercial Licenses by tylersmith on Wednesday September 13, 2017 @06:03PM (#15243156)
I was pleasantly surprised at how quickly I was able to rip out Caddy and replace it with nginx and Traefik (in different cases), even with the LE automation. It shouldn't be much of a burden to move your person projects I don't think.
[ Parent | on HN ]
Re:Announcing Caddy Commercial Licenses by folago on Thursday September 14, 2017 @06:23AM (#15246498)
Seconded. This is also how I felt reading the news.
[ Parent | on HN ]