-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude .sass and .map files from distributable zip #579
Comments
@bridgeport Thanks for the reminder. :-) We'll work towards updating our build script to exclude those files. You're right that they're not needed in the distributable zip. |
Next Actions
|
@raamdev While working on this issue you can take note of the FileSet tag provided by Phing and learn more about how |
Noting that this GitHub Issue should not be closed until the ZenCache Pro repo has been updated to include the latest build script changes (namely everything from wpsharks/phings#15, but also the changes from wpsharks/phings#17 which addresses this particular GitHub Issue). GitHub Issue to track updating ZenCache Pro with latest Phing build script is here: https://github.com/websharks/zencache.com/issues/72 |
See wpsharks/phings#15 wpsharks/comet-cache#579 websharks/zencache.com#72
See wpsharks/phings#15 wpsharks/comet-cache#579 websharks/zencache.com#72
Build script has been updated and I've confirmed that the |
Next Pro Release Changelog:
|
ZenCache v151114 has been released and includes changes from this GitHub Issue. See the v151114 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#579). |
The latest ZenCache pro v151002 looks great. The stats section and admin bar are very slick and informative.
However, it looks like it was packaged with the .sass and .map files. An oversight perhaps?
Location of the .sass files and directories:
Location of the .map files:
The text was updated successfully, but these errors were encountered: