Aim is to have git push to deploy working.
This involves processing source with hugo sever side.
Currently a number of issues.
each site has a different theme name, may simplify things to keep theme called bunait, even though each site will end up with a custom version.
bunait uses hugo to Postcss process css differently when hugo is in server mode vs staging or production, so cant process server side without Postcss and node.js.
can commit processed css and js to git instead, but hugo still tries to process source files on server at deploy.
What's the solution?
don't use hugo-extended? Set up automated processing external to hugo?
build with extended, commit generated resources, build with normal hugo on server...but how to include resources in templates so hugo knows to run postcss etc?
Changed hum script so the theme name bunait is retained with each new site.
Both hugo and hugo-exteneded currently always process postcss, so the only way forward is making sure node and postcss are available for the server side build. (Different from Sass processing.)
Thus committing processed css is pointless at present.
Aim is to have git push to deploy working. This involves processing source with hugo sever side.
Currently a number of issues.
What's the solution?