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 made a webapp using leptos and axum, today I had to deploy the app but I had to set it up to go through nginx.
I was instructed to serve the app on a server separate from the server running nginx, and I have to redirect all the requests made to the nginx server with the route prefix "/ems" to the other server running leptos.
I got the nginx configuration running but then realized the requested HTML page won't prefix its request routes with "/ems", which means it would never find any of its resources to be able to run the app. Is there a way I can fix this?
For more context, the leptos server is running on 192.168.2.160:3000, and this is the nginx configuration block responsible for handling the requests:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have made a webapp using leptos and axum, today I had to deploy the app but I had to set it up to go through nginx.
I was instructed to serve the app on a server separate from the server running nginx, and I have to redirect all the requests made to the nginx server with the route prefix "/ems" to the other server running leptos.
I got the nginx configuration running but then realized the requested HTML page won't prefix its request routes with "/ems", which means it would never find any of its resources to be able to run the app. Is there a way I can fix this?
For more context, the leptos server is running on
192.168.2.160:3000
, and this is the nginx configuration block responsible for handling the requests:Beta Was this translation helpful? Give feedback.
All reactions