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.
This PR introduces a new
max_crate_size
(under[general]
) configuration option to control the maximum allowed crate size upon publication.This configuration option can be expressed as either a single number (in bytes) or as a string with a specific file size unit.
It is also possible to omit this field to disable any file size limits.
This configuration option only applies to crate tarball sizes, it doesn't apply this size limit to any other request payloads in the API.
Therefore, it is still recommended to run Alexandrie behind a reverse proxy server and set it to limit the size for all incoming HTTP request body.
Here are some examples of accepted values:
Closes #98.
Closes #151.