We currently have to configure soul to overcome CORS requests.
But, if we served the static built react-admin as a soul extension, all requests would come from the host url.
Extensions are documented here: https://github.com/thevahidal/soul/blob/main/docs/extensions-examples.md
The big-picture is to:
- build a production release of the react-admin app, yarn build . The compiled app will end up in the build folder
- copy this built folder into a sub-directory of Soul
- create a Soul extension to open index.html on the built app
- call the Soul extension API, and check it:
a) serves our app
b) connects to Soul API
For that deployment strategy, we can probably even simplify the react-admin setup, since we don't need to specify the IP/Port for the soul server - it's the current one 🙂
We currently have to configure
soulto overcome CORS requests.But, if we served the static built
react-adminas asoulextension, all requests would come from the host url.Extensions are documented here: https://github.com/thevahidal/soul/blob/main/docs/extensions-examples.md
The big-picture is to:
a) serves our app
b) connects to Soul API
For that deployment strategy, we can probably even simplify the react-admin setup, since we don't need to specify the IP/Port for the soul server - it's the current one 🙂