In a headless setup we use KirbyCMS on a subdomain. The licence was activated with that subdomain. Unfortunately, but understandable the licence wont inherit to the staging-subdomain in that case. So i guess we have to activate the licence on the TLD, also if this is not directly the KirbyCMS-Site?
Would that be ok?
Tnx.
Current structure: www.project.com (None-Kirby) content.project.com (KirbyCMS, licenced) staging.project.com staging-content.project.com (KirbyCMS should inherit licence)
Inheriting a license is not possible, but you don’t need a license for staging sites. So the license needs to be registered to the live domain where Kirby is running.
In my opinion the Kirby licence file inherits to subdomains.
I remember that i already read that years ago.
At least to not have the register-note at the bottom of the panel in a staging-version of the site.
I know that i don’t need the licence for a staging-version, but it’s a bit annoying, if the customers always ask, why we don’t have an activated licence in the staging-panel.
I just had a look in one of my non-headless-projects.
The licence in the System-View in the Panel ist also ‘green’ in the staging-version. There is also no register-note at the bottom in that panel. (subdomain of the licenced tld)
That is what i wanna achive, but it is not possible in headless-projects, if the licence is already activated on a subdomain like content.xyz.com
But in my case, it is not another project, just another domain setup
And the cms on the subdomain is the provider for the tld.
Without that, the frontend is relativly empty
So technically, the licence is needed for the tld
Yes, I know, forwarded your question to the team. What I meant was that mydomain.xyz and blog.mydomain.xyz and finance.mydomain.xyz could be totally different projects that might each require their own license. So I doubt there is something like automatic inheritance of licenses to subdomains.
There is indeed logic to accept some subdomains (currently www, dev, test and staging) for a license registered without subdomain. You can find this logic here:
However, as you already discovered, this doesn’t work if the license is registered to another subdomain such as content.. We are aware of this limitation and have plans to improve the setup to allow additional activations for staging or testing sites at no additional cost. But this is not something we can fix quickly, it needs some restructuring of our license setup.
Yes, i thought so that there is a limitation to dev/stage/staging... or whatever limits you set.
In my case or headless-cases in general, it could be easy to activate the licence with the TLD. If you slightly update the limits of subdomains and add content.xy.com, ‘staging-.xy.com’, 'dev-.xy.com’ the probs would be solved.
To be honest we can’t really extend that list as every customer will require different subdomains, they are not standardized. Sorry for the inconvenience.
