Add compression level setting to enhance archive size optimization #256
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 17, 2024 08:58
…utput size when compressing application on MacOS
… maximum for better efficiency
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Optimize the ZIP process to maximum compression available.
Reason for this is that my MacOS machine Application size is bigger than the same application compressed via @fideloper his ChipperCI.
Lot of times my application size is too big for Lambda and Vapor CLI tells me to make it a Docker, but I prefer Lambda and that's possible when I deploy the same application with ChipperCI.
There is a support ticket about it which is handled and investigated by Josh.
Or use
tarinstead ofzipon MacOS. But that unzipping is probably done at after Vapor-CLI does it's job.