What HashiCorp’s License Change Means for Spacelift Customers

Re:What HashiCorp’s License Change Means for Spacelift Custo... by orthoxerox on Friday August 11, 2023 @10:31AM (#37089101)

Not really, just push the tarball with sources to nginx when you deploy a specific commit.

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by sitzkrieg on Friday August 11, 2023 @11:27AM (#37089779)

yea this is definitely user friendly and realistic

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by jen20 on Friday August 11, 2023 @11:40AM (#37089951)

If 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.

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by post-it on Friday August 11, 2023 @12:20PM (#37090463)

Glad you agree.

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by Vespasian on Friday August 11, 2023 @11:41AM (#37089955)

You 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.

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by yencabulator on Saturday August 12, 2023 @02:24PM (#37102846)

There are AGPL software vendors who think making HTTP requests to their AGPL software forces you to license the client as AGPL too.

[ Parent | on HN ]