Hello everyone,
While adding support for data residency to our Connect app, we encountered a rather difficult situation, for which I’d like to get some feedback from the community, because I don’t think we’d be the only one to experience this.
Supporting data residency in a Connect app requires different domain names, for the different regions. This is usually handled by having 1 domain, and using a subdomain prefix for the regions, for example example.org being the main domain of the app, and us.example.org, eu.example.org, etc. being the domains for the specific regions. As far as I know, this setup is the one recommended by Atlassian as well.
During development of our frontend code, we run the frontend locally, use ngrok to create a tunnel, and install the app using the tunnel’s url. This process used to work perfectly for years, my colleagues told me it was even recommended by Atlassian at some point in the past to do it like this. (I did not research this statement, but it doesn’t sound far-fetched.)
However, the free plan in ngrok doesn’t support having subdomains for a tunnel, and as far as I know, only the biggest Enterprise plan has wildcard domains, which costs a fortune.
We are currently investigating possible alternatives, but in the meantime, I wanted to ask the community:
Did you guys encounter this problem as well? How did you solve it?
Do any of you have a tried-and-proven alternative, that doesn’t cost a fortune?
Thank you for any and all answers.
Regards,