feat(infra): move backend url from build time to runtime #54

New issue

Open

opened 2026-01-28 20:57:10 +00:00 by chartgerink · 0 comments

chartgerink commented

2026-01-28 20:57:10 +00:00

Owner

Currently, the backend is baked in on build time (either manual build or docker build).

This makes especially the docker image less valuable, as it is not portable from one to the other backend. It even makes it strenuous in the situation of testing etc, as each has to have their own docker image.

It would be great if we could find a way to make it work in runtime, such that it is portable. It would even be sufficient if we could simply know it is always on the /api path for the origin of the frontend (for example, https://researchequals.com -> /api and https://test.researchequals.com -> /api)

Currently, the backend is baked in on build time (either manual build or docker build). This makes especially the docker image less valuable, as it is not portable from one to the other backend. It even makes it strenuous in the situation of testing etc, as each has to have their own docker image. It would be great if we could find a way to make it work in runtime, such that it is portable. It would even be sufficient if we could simply know it is always on the `/api` path for the origin of the frontend (for example, `https://researchequals.com` -> `/api` and `https://test.researchequals.com` -> `/api`)