I am an Indy developer, and have a number of installations now out there in the wild, and I find it a bit difficult to update my end customer’s system with the license key when I renew. Is there a better strategy to deal with this? Like build a license key service? How would that work considering you can’t really boot up without it.
You only need to update the license key when you upgrade ServiceStack to a version that has was released after its configured license key expires. So if you don’t upgrade your existing Apps you don’t need to update its License Key.
ok this helps me better understand the when it is needed but I am curious how others are solving the how when dealing with more than a handful of runtime environments. I am thinking it might just be best to hard code it and have the pipeline inject it from dev environment?
If you’re hard coding it in your projects source code your CI shouldn’t have to inject anything? i.e. It’s already configured with it.
The other option is to set the SERVICESTACK_LICENSE Environment Variable which should be fairly trivial to do with any CI environment / GitHub Action / etc.
We use AWS Secrets Manager to dynamically load keys (for SS and other libraries).