Stacks Licensing - Githubissues

joeworkman commented 6 years ago

I am pretty sure that this is on your radar. But the ability to license stacks could be useful. I would be happy to revisit how I do this for Total CMS if it can be made better.

yourhead commented 6 years ago

any suggestions or requirements that you have would be helpful.

joeworkman commented 6 years ago

Currently Total CMS is licensed per domain. In order to accomplish this, Total CMS "phones home" once per day to verify that Total CMS is licensed to run on the domain. I have built in a back door so that this process could fail for 30 days before Total CMS will stop saving data to the CMS. So if my server were to ever go down, I have 30 days to get everything back up and working before anyone is affected.

However, as morbid as this seems, people have been talking on the forums about my death. What if I were to die tomorrow, the current way Total CMS is licensed could be an issue.

Maybe my current system is overly complicated? I don't know. I am open to ideas...

What if this were all possible inside Stacks? Some random thoughts to get the ball rolling...

The user adds the license key into a license setting.
Maybe there could be a new setting type that has a button that the user could submit the license to verify that its valid. It would make a standardized REST API call to my server in order to verify that the license is correct.
The website address of the project would have to be sent along with the license key.
If the license is valid, the project will publish properly.
If the license is not valid, then the stack that contains the license verification would not be published
Or there could be new Stacks API macros to display different contents based on the license being valid. %[if licensed]%

yourhead commented 5 years ago

see: https://github.com/yourhead/s4/issues/43

yourhead / s3

Stacks Licensing #788