You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where I would like my main application to call API endpoints exposed by the application running within the Webcontainer and vice versa. When my host server is running locally at localhost:3000 and I call fetch("http://localhost:3000/api/...") from within the Webcontainer, obviously it doesn't work, because that API endpoint does not exist within the container.
I already thought of a few rather "hacky" solutions, such as:
Writing a file to the Webcontainer's file system whenever I want to communicate with it, and polling for changes within the Webcontainer.
Using some sort of reverse proxy, so that e.g. "myapp.example.com" is forwarded to my host application running on localhost, and then I could just fetch "myapp.example.com" from within the Webcontainer.
But there must be a better solution for this kind of basic HTTP communication between host and container. How do I do this?
The text was updated successfully, but these errors were encountered:
I have a use case where I would like my main application to call API endpoints exposed by the application running within the Webcontainer and vice versa. When my host server is running locally at localhost:3000 and I call
fetch("http://localhost:3000/api/...")
from within the Webcontainer, obviously it doesn't work, because that API endpoint does not exist within the container.I already thought of a few rather "hacky" solutions, such as:
But there must be a better solution for this kind of basic HTTP communication between host and container. How do I do this?
The text was updated successfully, but these errors were encountered: