Deploying with react router-- endless rabbit hole

netlify.toml:

[build]
command = “npm run build”
publish= “gh-pages -d build”
base = “path-to-react-app”
(name of my project is portfolio… should that be my base.?
[[redirects]]
from = “/*”
to = “/index.html”
status = 200
the following is my last log: been banging my head for 2 days… Help…
Found Netlify configuration file(s). Overriding site configuration
9:55:50 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: ‘path-to-react-app/build’ versus ‘build/’ in the Netlify UI
9:55:50 AM: failed during stage ‘building site’: fork/exec /usr/local/bin/build: no such file or directory
9:55:50 AM: Different build command detected, going to use the one specified in the Netlify configuration file: ‘npm run build’ versus ‘gh-pages -d build’ in the Netlify UI
9:55:50 AM: Different base path detected, going to use the one specified in the

End of Last log:
Netlify configuration file: ‘path-to-react-app’ versus ‘dev_portfolio/’ in the Netlify UI
9:55:50 AM: Starting build script
9:55:50 AM: Build command unable to start
9:55:50 AM: Shutting down logging, 3 messages pending

Hi, @deScamuS, and welcome to our Netlify community site.

The setting about for build.publish is “gh-pages -d build”. This is a build command and not a directory which is what is expected for that setting.

There is more information about the netlify.toml settings here:

https://docs.netlify.com/configure-builds/file-based-configuration/

Would you please try changing the “publish” setting to the directory where the static content to be served will be found after the build command completes successfully?

If that doesn’t help and/or if there are other questions, please reply anytime.

Hi Luke! Thanks for getting back to me… ended up just publishing to github for this …but plan on using netlify for future deployment— thx again