Due to build filename MD5 hashing, Basset is incompatible with load balanced environments #234
Description
Basset has been working great for us until we decided to roll this live. We have a 3 server load-balanced environment. If one server gives the user the HTML file but another tries to serve a CSS or JS asset that was "built" by Basset then it fails. That is because the build name on one server will be different than on the other.
I looked into using a filter to fix this. But that is not possible because the name is determined and set AFTER the filters are run. I checked for a configuration option for setting file names or the option to pass in a method or closure, but neither is available. The naming method is hard-coded in.
Then I tried checking for post-build options. But there do not seem to be any. So I guess I will have to find another solution. Prior to this Basset has been great. Frustrating.
I would recommend adding in a way to specify file names or generate symlinks with a core name to reference and return. Or, Basset could even allow a function, a post-run filter, or a closure to handle the file naming as a secondary option.