I'm not complaining about CSS in Resource Registries.
Ok, I am. Just a bit. I thought I understood, and now I don't.
I have a css file on my filesystem, and I made a change to it. I want to deploy this change to production. I push to git, bla bla bla, and new css file appears on production environment.
Production doesn't change, the default.css doesn't change, nor does the timestamp.
On production, I visit @@resourceregistry-controlpanel and click 'development mode', save, and uncheck development mode and try again.
Timestamp changed! but not default.css. gurr. I still see my resource in default.css, but it's the old CSS.
Restart plone - nope. CSS still the old one.
Check the filesystem, yep - the CSS is good there.
Go back to @@resourceregistry-controlpanel , click 'overrides' and look at the resource. The CSS looks good there too! I don't override tho - that defeats the purpose. Just noting that the TTW editor sees my on-disk changes.
check development mode again, check 'develop css' on my bundle with the css resource, click 'save'.
Refresh - NO CHANGE!
Stop the server, start PRODUCTION with /bin/instance/fg
Now, I get this message
[Products.CMFPlone.resources.browser.combine:156][waitress] Wrote combined CSS bundle "default". Good!
Refresh page - and wow! Now I have my changes!
stop server, ./bin/instance start, and now we are all good.
Question: What is the NORMAL procedure to deploy a CSS change to production? Mine is a bit, well, odd.