How to change URL for Retype app?

[yohny]

We have a Retype app that holds our documentation hosted in Azure static websites. All worked fine until recently when we changed our custom domain where the page is hosted. When I change the url value in .retype.yml to the new domain, the retype build cmmand starts failing with

ERROR: The specified secret is not valid for the "url" config host: "new-domain.example.com".

We have our secret in environment variable RETYPE_SECRET. What is the problem? How is the secret tied to the domain?

[geoffreymcgill]

Hi @yohny,

The Retype Pro key is purchased for and associated to a specific domain and/or sub-domain name. If you revise the project url setting to a new value, the key will not verify for that new url and you will get the console ERROR message you are seeing now.

Please send an email to hello@retype.com with your old and new url values and we will investigate right away.

Hope this helps.

[yohny]

thanks for the information @geoffreymcgill
It seems that url value is only important for secret verification, but not actually for the verification of the domain where the retype app is actually running as our retype app runs just fine on the new domain. Whats then the actual purpose of having the secred tied to the domain? Even the generated CNAME file can be customized to use different value than url.
In the Retype documentaton I can no loger find any mention of RETYPE_SECRET, instead I see there RETYPE_KEY - is the migration needed?

[geoffreymcgill]

Additional url and domain verification may be added in the future.

In the Retype documentaton I can no loger find any mention of RETYPE_SECRET, instead I see there RETYPE_KEY - is the migration needed?

The RETYPE_SECRET environment variable was renamed to RETYPE_KEY but the old RETYPE_SECRET is still supported to ensure backwards compatibility and no breaking changes. There is no issue using RETYPE_SECRET but we removed from the documentation to focus on the consistent use of RETYPE_KEY. If you can, please update your project to use RETYPE_KEY instead of RETYPE_SECRET.