Best licensing approach for site migration to kirby

The CMS Questions
1

I’m currently migrating my site to Kirby and would like to understand how the licenses work. Here’s the context:

Before fully migrating, I plan to upload my Kirby project on a subdomain dev.mydomain.xyz and keep mydomain.xyz non-Kirby until the development is complete. Once the development is done, I intend to remove dev.mydomain.yxz and move my development to mydomain.xyz.

What’s the best approach regarding the licenses?

  1. Activate the license on the instance at dev.mydomain.xyz with mydomain.xyz as the reference domain. The license will remain active when the site goes live.
  2. Activate the license on the instance at dev.mydomain.xyz with dev.mydomain.xyz as the reference domain. Then, change the license reference when the site goes live.
  3. Only activate the license once the site is live on mydomain.xyz.
  4. Only develop locally.

Thank you for your help.

2

Option 3, ideally, dev.mydomain.xyz would be behind basic auth, you don’t really want to leak this before done.

1 Like