-
Notifications
You must be signed in to change notification settings - Fork 24
flexibility of port and subpath #337
Comments
You can configure where the frontend looks for the backend in Note if you're not serving the frontend on the same domain as the backend you'll also need CORS configuration, you can set the |
I did the change in the confiig.js and rebuilt the Docker image. Unfortunately it still asks for /api and /cable instead of /postfacto/api and /postfacto/cable. Any additional hint? |
Meanwhile could figure out why the Docker build doesn't work. The config.js is generated by the entrypoint. You need to adapt the entrypoint to do the changes suggested above. But even then it still doesn't work. I also tried to modify the package.json with "homepage" tag to move the frontend. But still postfacto doesn`t work. I also recognized that the admin part is another story as it shows different paths as the main app. So, the question remains: Is it possible to move backend and frontend to a different subpath? |
That's right, if you're using the Docker build the Changes made in there should be reflected in the response when the React app makes a request for the And yes, the admin UI is still at |
I did several approaches meanwhile but unfortunately without final success. Here is what I've changed so far:
By doing so I now receive for all calls in my browser a status 200, which should be fine, but the page unfortunately states "Oh no! It's broken". Do you maybe have further suggestions? |
I would like to bind the postfacto ui to "myserver.de:8000/postfacto".
Is there any possibility to do this by changing only small configuration things?
The text was updated successfully, but these errors were encountered: