[mholt]

Thanks for your feedback. Really appreciate it.

> Does anyone know if there's significant pain in maintaining a docker image that compiles source code like Caddy on rebuild?

Yes, Cory specifically is looking into the ability to get custom distro packages and containers through our website for our customers.

Totally understand about bootstrapping a business and the costs there. Feel free to contact us: [e-mail] since your business is just starting out and doesn't have any revenue yet, and we'll see about a custom plan that fits you better.

[jimangel]

Thanks! While I appreciate the offer to work with sales, it really abstracts the simplicity of Caddy (ex: grab this binary, add these couple lines, and BAM you have a site).

I want to shout from the rooftops about Caddy and how awesome it is to effectively roll out side projects. If I had to create a blog post saying "contact sales if you're just starting out" at the end, it would leave a bad taste in my mouth.

An amazing part of the open source tech community is the ability to read a blog post, put the concepts together, and see the light (or not). I've grown so much as a professional by reading blogs, forums, etc and I'd love to give back. Before today, Caddy stripped away the complexities of maintaining a webserver and allowed entrepreneurs to focus on what matters. This move appears to add the complexity back in for those who want to still use it as open source.

Once again, love the work you've done on the project and understand the desire to make money. IMHO a model similar to nginx or an "honor system" (companies generating more than X revenue need to purchase a license) would be better.