3 ms·
Not really, just push the tarball with sources to nginx when you deploy a specific commit.
by orthoxerox 3y ago
Not really, just push the tarball with sources to nginx when you deploy a specific commit.
- sitzkrieg 3y agoyea this is definitely user friendly and realistic
- jen20 3y agoIf you make modifications, and deploy them in a way accessible to a given user, the changes must be made available to that user. I fail to see what is unrealistic about that, or indeed user-unfriendly, unless you consider the user to be the developer and not the person on the other end of the wire.
- post-it 3y agoGlad you agree.
- arlcode 3y agoYou don't even need to do that immediatly afaik. You can wait for the first person to request the source and do it then manually (or link to the nginx github). Most likely that will never happen for most people who deploy it. After all it's a pretty good price for what you are getting in exchange.
- yencabulator 3y agoThere are AGPL software vendors who think making HTTP requests to their AGPL software forces you to license the client as AGPL too.