This pull also removes the old client and replaces it with the FSSK-React-Client.
The production build now does a prod build of the client and copies the important stuff instead of needing node/npm in prod container.
I was totally on the wrong path with messing around with Apache, reverse proxies, .htaccess, url aliases etc. With Jared's help, it was as simple as making sure FSSK-React-Client production build was building with the "homepage": "/client" tag. Otherwise, the server/public/client/index.html file would have the client side routing taken over by Laravel. My first instinct was, "Oh, there's a rewrite/redirect problem!" when it really was just a configuration problem.
(I also noticed that editing/updating a TODO list isn't quite working correctly - this is true for the FSSK-NODE app as well.)
This pull also removes the old client and replaces it with the FSSK-React-Client.
The production build now does a prod build of the client and copies the important stuff instead of needing node/npm in prod container.
I was totally on the wrong path with messing around with Apache, reverse proxies, .htaccess, url aliases etc. With Jared's help, it was as simple as making sure FSSK-React-Client production build was building with the "homepage": "/client" tag. Otherwise, the server/public/client/index.html file would have the client side routing taken over by Laravel. My first instinct was, "Oh, there's a rewrite/redirect problem!" when it really was just a configuration problem.
(I also noticed that editing/updating a TODO list isn't quite working correctly - this is true for the FSSK-NODE app as well.)