smashercosmo
commented
4 years ago This what I do on my Gatsby site. Maybe this can help you:
cms.js
const config =
process.env.NODE_ENV === 'development'
? { local_backend: { url: 'http://localhost:8000/api/v1' } }
: {
backend: {
name: 'git-gateway',
branch: process.env.GATSBY_BRANCH || 'master',
},
}
CMS.init({ config })gatsby-config.js
// process.env.HEAD comes from Netlify
process.env.GATSBY_BRANCH = process.env.HEADIn your case I think you can just simply
const config = {
backend: {
name: 'github',
branch: process.env.HEAD || 'master',
repo: 'Axway/axway-open-docs', //Path to your GitHub repository. For fork testing use alexearnshaw/axway-open-docs.
open_authoring: true,
},
publish_mode: 'editorial_workflow',
media_folder: '/static/Images', // Media files will be stored in the repo under static/Images
public_folder: '/Images', // The src attribute for uploaded media will begin with /Images
site_url: 'https://axway-open-docs.netlify.com/', // for fork testing use https://fork-axway-open-docs.netlify.com/
collections,
};
// Make the config object available on the global scope for processing by
// subsequent scripts.Don't rename this to `CMS_CONFIG` - it will cause the
// config to be loaded without proper processing.
window.CMS_CONFIGURATION = config;
CMS.init({ config })
erezrokah
alexearnshaw
We are using Netlify CMS open authoring workflow for our open documentation site https://axway-open-docs.netlify.app/docs/
We are using Hugo to generate the site and Netlify to deploy and host. We are using Netlify CMS to enable contributors to edit our docs directly (via pull requests from their own forks)
We now have a requirement to have multiple branches in our Git repo, as we need a way to enable internal contributors to edit docs for new features in our product that are in development/not yet released. We need a way to allow contributors to edit these docs but we don't want to merge them to production until a certain point in time.
Our repo is https://github.com/Axway/axway-open-docs and our Netlify CMS config is implemented here https://github.com/Axway/axway-open-docs/blob/master/static/admin/config.js
I've read through all of the comments on these existing issues decaporg/decap-cms#1737 and decaporg/decap-cms#1795 but I think these solutions are not exactly what we need as we are looking for something simpler...
This is what I think we need:
My question is - is this as simple as just having a different Netlify CMS config on each branch, that sets the branch for Netlify CMS to development on the dev branch and to master on the production branch? Will this become a headache when we are trying to keep the two branches in sync? Or is there a better way/recommended way of handling this use case in Netlify CMS?
I'd really appreciate any advice/best practices on how others have done this. Thanks in advance!