Summary
It would be great to be able to configure the Strapi backend URL after the admin bundle has been built.
Why is it needed?
It will allow for a more flexible deployment, using the same build artefact for multiple deployments, when using separate URLs for backend and frontend, which we do. This will also make it easier to make a pre-built docker image.
Suggested solution(s)
I suggest making it possible to specify a URL where the backend URL can be fetched. On deployment, a file containing the URL could be placed on the specified URL, which will let Strapi determine the URL for the backend on initialization.
For example, the first thing the Strapi admin bundle would do could be a GET request to /backend-url which could respond with a URL to be used. Then on deployment, all we need to do is to deploy the backend-url-file along with the bundle.
Created by Derrick Mehaffy