Issue #8121 has been updated by Daniel Pittman. Status changed from Accepted to Rejected
There is no way to create all.css, and other cached CSS and JS content, than the way we are doing it. If this is not being created correctly, this is a Rails bug. I believe we arrange things so that SASS is only required on development machines, so it may be that you don't have it installed on your system? I don't believe it is in vendor. Either way, there isn't anything else for us to do about this. ---------------------------------------- Bug #8121: We aren't correctly creating all.css in production mode https://projects.puppetlabs.com/issues/8121 Author: Nick Fagerlund Status: Rejected Priority: Normal Assignee: Category: Target version: 1.2 Keywords: Branch: Affected URL: Affected Dashboard version: When running in production mode (under passenger), deleting all.css will first result in a 500 error, then (on a second reload of the page) result in completely unstyled content. Checking all.css shows that it got re-created, but is blank. This came up because all.css wasn't showing the correct styling for tabs, which should have been in application.css, and doesn't seem to have made it there from application.scss. Application.css never came back after we deleted it, and since all.css isn't being created directly from sass, it fell over after that. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
