Thanks Tom, I gave that beta feature a go.
This is likely my tough biscuits issue to work through, but just throwing it out in case anyone knows why its not working.
local_backend: local to my config.yml.
Then installed the netlify-cms-proxy-server
And it ‘seems’ to run (although not much verbiage, as per below)
Yet it doesn’t seem to generate a site.
When I try to view localhost, it just gives me,
Cannot find /
Out of desperation, I tried the custom port suggestion.
So I added an .env file containing PORT=8082.
My config.yml (top of it):
# when using a custom proxy server port
My package.json commands:
"debug": "DEBUG=*Error* npx @11ty/eleventy --dryrun",
"start": "npx gulp && concurrently 'npx gulp watch' 'npx eleventy --serve'",
"build": "NODE_ENV=production npx gulp && NODE_ENV=production eleventy",
"dev": "npx netlify-cms-proxy-server"
My server message looks sparse:
> npx netlify-cms-proxy-server
info: Netlify CMS File System Proxy Server configured with /home/chris/projects/french.plus/website
info: Netlify CMS Proxy Server listening on port 8082
There doesn’t seem to be any network traffic related to my site.
Hence, since I’m running eleventy, I wondered if it needed ‘eleventy’ in the package.json file.
Eg. I tried various permuations, such as:
"dev": "npx netlify-cms-proxy-server eleventy"
But no luck.
Anyone have any ideas/suggestions?