So dce-config.js in theory gets reset every time dce is update as postinstall overwrites the previously defined collections/settings in dce-config.js.
This is mostly just an issue of being a noob, but how might we at least start off dce-config.js' collections definition by pulling collections from docpad.coffee, something along these lines (commented out portion here on line 15, docpad.collections...):
https://github.com/MassDistributionMedia/docpad-plugin-dce/blob/master/dce-config.js#L15
I know we're using dce-config.js to set auth and collections but with the power of docpad.collections pulling collections from docpad.coffee, maybe we can make the dce-config.js even simpler by omitting the collections definition portion.
(Using the docpad downloader plugin to install the basicauth plugin to /node_modules may make more sense than baking basicauth into dce also following the philosophy to keep things as modular as possible: https://github.com/docpad/docpad-plugin-downloader )
So dce-config.js in theory gets reset every time dce is update as postinstall overwrites the previously defined collections/settings in dce-config.js.
This is mostly just an issue of being a noob, but how might we at least start off dce-config.js' collections definition by pulling collections from docpad.coffee, something along these lines (commented out portion here on line 15, docpad.collections...):
https://github.com/MassDistributionMedia/docpad-plugin-dce/blob/master/dce-config.js#L15
I know we're using dce-config.js to set auth and collections but with the power of docpad.collections pulling collections from docpad.coffee, maybe we can make the dce-config.js even simpler by omitting the collections definition portion.
(Using the docpad downloader plugin to install the basicauth plugin to /node_modules may make more sense than baking basicauth into dce also following the philosophy to keep things as modular as possible: https://github.com/docpad/docpad-plugin-downloader )