6 ms·
Exactly, building and pushing to GitHub is a set-and-forget process. Besides, it already needs to be done for paying customers now so what kind of work is that
by gtirloni 9y ago
Exactly, building and pushing to GitHub is a set-and-forget process. Besides, it already needs to be done for paying customers now so what kind of work is that saving Caddy? I don't understand.
EDIT: Additionally, it's an error to think that non-paying customers are not contributing. It's actually a pretty basic misunderstanding for an open source company. Users are contributing with bug reports, small fixes, testing, marketing, etc. It amazes me we still see this feeling in 2017. I dare all companies with open source projects to actually close them and replace non-paying customers with QA teams, more developers, more infrastructure, etc. Make sure to increase your budgets and raise your prices accordingly.
- iampims 9y agoAnswering my own question: it is now my understanding that caddy relies on a custom build system to generate custom builds on the fly for its plugins. Publishing all combinations on GH wouldn't make much sense given the combination explosion for any new plugin.
- gtirloni 9y agoThat's excellent. Most people don't seem to use plugins so a default build is enough for them. Those who need it have a business need now and can either setup their own build system or pay Caddy for that. Value is generated as opposed to being subtracted (from the current status quo).