Saleor Dashboard deployment to Vercel / Netlify #2446
-
|
Hey guys and gals, Trying to deploy Saloer Dashboard to production, with both Vercel and Netlify, It works ok, I can login, add, edit etc. in the dashboard... but. If an Action requires I open a link e.g. vercel.example.com/configuration, OR i refresh i get a 404 Page not Found. Saleor Dashboard works when i run it locally, that is on localhost:9000, I have no problems refreshing or opening URLs further into the dashboard. My conclusion right now is, that it has something to do with how both Vercel and Netlify build the project. I should mention, i have added the environment variable API_URI which links to my Saleor Core Server Deployment on Vercel Got to the link or refresh and i get this error Vercel build configuration Deployment on Netlify Got to the link or refresh and i get this error Netlify build configuration |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi @Horib , have you set 404 custom page? Dashboard uses React Router under the hood to render different pages under different paths, but that's done exclusively in browser (as this path doesn't exist as something routable on a server). In that situation you have to redirect all 404s your server is getting to |
Beta Was this translation helpful? Give feedback.
-
|
I think it's because vercel doesn't know that you have an SPA app. In the SPA we need to tell the server that all traffic must go to the index of the app. It's the same for any reverse-proxy / web-servers, otherwise, a web-server will try to match based on the filesystem. Here is more info https://vercel.com/docs/project-configuration#project/rewrites I think for you will work (vercel.json): {
"rewrites": [
{"source": "/(.*)", "destination": "/"}
]
}So you basically rewrite everything in the URL always to |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic it works :) thank you very much |
Beta Was this translation helpful? Give feedback.
I think it's because vercel doesn't know that you have an SPA app. In the SPA we need to tell the server that all traffic must go to the index of the app. It's the same for any reverse-proxy / web-servers, otherwise, a web-server will try to match based on the filesystem.
Here is more info https://vercel.com/docs/project-configuration#project/rewrites I think for you will work (vercel.json):
{ "rewrites": [ {"source": "/(.*)", "destination": "/"} ] }So you basically rewrite everything in the URL always to
/which is understandable by the server (index), where also SPA lives.