Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
When rpm installation occurs, old sprockets manifests should be deleted #42
On webtest04 the rpm that is currently installed provides only one sprockets manifest file:
However, during deployment, the previously existing sprockets manifest file is still there:
The result is that Rails is loading the older manifest. The code used to load that is here:
The result of picking the wrong manifest is that the HTML includes the wrong path to the recently updated asset i.e.
This is produced by Rails looking at the older
@ericfranz Per my email comments, there's not much we can do if sprockets are getting created that are not part of previous RPMs. The files that existed both at OSC and TAMU are not a part of any RPM we've ever built so they have to have been generated outside packaging which means there's not much to do for packages.
If we wanted to come up with a way to clean old sprockets, we'd run the risk of deleting files that do belong to RPMs which will generate errors during RPM updates. The names aren't static in the two cases so if we just did "rm /path/to/.sprockets-manifest*" we'd run the risk of deleting packaged files and thus generating RPM validation errors.