Just confirming that the “closing” of the file is on the target not the source?
I wanted to reseed test server, but wanted to ensure that production is not interpreted.
The “build” is on the server with the “source” files.
Hope that helps
Thanks
Todd
Thanks
Could we add where things are opening and closing (source / target ) ?
Also why does the sliders for Compression & Memory don’t align if they both are set tot the same level?
The “close files during build” is not represented in the deployment log as we are not including the build log in that deployment log. So everything in the deployment log is happening on the destination server. The Files on the source are being closed in the “Build running” portion of that log. We could presumably include the build log and add the information about where the files are closing, but I think including the build log there increases confusion rather than decreasing it.
As for the sliders not lining up, its because they have different ranges. Compression level goes from 0 to 9, while memory goes from 1 to 9. This is because you can have no compression, where it makes a zip file but does not actually do any compression of the data (this is faster and less memory intensive than adding compression, but makes a file slightly larger than the sum of its contents sizes due to a bit of metadata), whereas you always need to use some memory. I appreciate that it is slightly weird, but this is the standard setup for the zipping we’re using under the hood.
-Kyle