It provides you with a starter which is setup to serve the React blog from the same-origin as the strapi server.
My motivation for this starter:
To achieve this, the starter is configured with a custom Strapi Middleware to serve the client on
/app and the admin on
The custom middleware is named clientView and is configured in the middleware config. The client only needs to be configured in one place, the package.json with a "homepage" setting to match the middleware config
targetPath. This gets applied to the React Router
To change the path the client is served on, change the middleware config
targetPath, and the client/package.json
The middleware also sets a redirect on root
Additionally, this starter adds a heroku-postbuild script which ensure the admin and client are rebuilt on redeploy. The strapi/react-starter-blog fails to rebuild the admin build on subsequent deployments.