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
Hi. I think this project is the foundation of the FastAPI integration tutorial, which I just completed. The problem with it is that it assumes the Panel server is visible by the web clients. That is, the document that FastAPI (or uvicorn) serves to the browser has URLs that point back to Panel (http://127.0.0.1:5000/app)
I need my FastAPI application to proxy Panel content, not simply re-direct to another address. The fundamental use case is a server running behind a firewall.
Is there a different way to serve the Panel content that doesn't require the browser hitting the Panel server process directly?
The text was updated successfully, but these errors were encountered:
Hi. I think this project is the foundation of the FastAPI integration tutorial, which I just completed. The problem with it is that it assumes the Panel server is visible by the web clients. That is, the document that FastAPI (or uvicorn) serves to the browser has URLs that point back to Panel (
http://127.0.0.1:5000/app
)I need my FastAPI application to proxy Panel content, not simply re-direct to another address. The fundamental use case is a server running behind a firewall.
Is there a different way to serve the Panel content that doesn't require the browser hitting the Panel server process directly?
The text was updated successfully, but these errors were encountered: