Can the local_backend property be left in the CMS config file during production?

I will be using the netlify CMS for local development using the local_backend property. Can I leave it within the config file during deployment?

AFAIK, the local_backend only kicks in when I run npx netlify-cms-proxy-server which won’t be run by Netlify during production deployments. So for both my local dev and prod builds, I can leave that statement in the configuration.

Or do I have to edit the config YAML file and remove it every time I’m done with local development and I’m pushing to my remote repo for deployment?

Is there an easy way to switch between the local and production git repo when I’m done developing?

Hi there! Thanks for your interest in Netlify CMS. Looks like you posted your question a little while ago, but that you haven’t received a solution yet. Here’s where you might get more help: - the site houses our extensive documentation that likely contains helpful information to get you back on track.

netlify cms slack - join our friendly slack channel and chat with other cms pros to get the help you need.

GitHub Issues - think you’ve found a bug, or would like to make a feature request? Make your voice heard here. Netlify CMS is open source - PRs and other contributions are also welcome!

Stack Overflow Check StackOverflow for questions tagged “Netlify CMS” if you don’t get an answer in the Slack or the GH issues. StackOverflow reaches a worldwide audience of knowledgeable people.

Your question will be left open here for anyone to comment - but we encourage you to check out the above resources if you are still looking for a solution!