this project was created using a gatsby starter, to generate a project with the same starter use:
$> gatsby new myproject https://github.com/fes300/gatsby-mui-netlifycms-template.git- init git:
git init(N.B. it is important to do this before the deps install so that husky can write its custom hooks) - install deps:
yarn - rename your project:
make rename name=$(YOUR_WEBSITE_NAME)
- start you local git repo (for local netlify admin):
npx netlify-cms-proxy-server - start project:
yarn start
yarn start triggers the command netlify dev that does a lot of things (like injecting the dev env set in netlify backoffice into your local runtime, simulating locally your lambda functions and more)
- make sure you have docker and docker-compose installed
- run
make startfrom the project root - access your local enwironment at
${YOUR_WEBSITE_NAME}.lvh.me(${YOUR_WEBSITE_NAME}.lvh.me/adminfor the cms backoffice)
at the moment starting the project with docker only runs yarn develp triggers the command gatsby develop, which means that some things will not be mocked (especially your lambda functions).