Why is Muse Publishing/Exporting/Uploading So Many Files?

Version 2

    Typically when using Muse and re-publishing, exporting or uploading Muse will determine the set of pages changed since the prior publish, export or upload and only generate the files related to those pages. Muse will then compare a “fingerprint” of the newly generated files to fingerprints for the files previously published/exported/uploaded to detect whether there were any differences and will only actually upload (or write out) the files that contain changes.


     

    So Why Is Muse Regenerating And Uploading Everything?!

     

    When you take an update of Muse, the HTML, CSS and JavaScript code generated by Muse will have changed for any number of reasons (i.e. to support new features, to workaround bugs in recent updates to popular browsers, to improve page load performance, etc.) and the image processing may have also changed (i.e. to improve compression, to improve quality, to use CSS rather than images where possible, etc.). Since the files that make up a website are all interrelated, the files need to all be from the same version of Muse in order for your website to function correctly. Therefore, after an update of Muse your next publish, export or upload will generate all the files for your site and then upload only those files with actual changes. Once this process has been completed once and the .muse file has been saved, all subsequent publish, export and upload operations will only generate and upload the files related to changes you’ve made since the last publish, export or upload.


     

    In short, after taking an update of Muse expect the next Publish, Export or Upload to be slow, but after that’s been completed and the .muse file has been saved, the next re-publish, export or upload will be back to normal, only generating files directly related to changes you’ve made.