chore: bump version to 0.2.1, restrict database host, and increase max file upload size to 100MB#180
Merged
ronibhakta1 merged 1 commit intoApr 16, 2026
Conversation
…x file upload size to 100MB
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
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.
This pull request includes a version bump and increases the file upload size limits across the API and Nginx, as well as tightening the Postgres service binding to localhost for improved security.
Version and configuration updates:
0.2.0to0.2.1inVERSION.Security improvements:
compose.yamlto bind to127.0.0.1instead of all interfaces, restricting access to localhost.File upload and request handling enhancements:
client_max_body_sizeindocker/nginx/nginx.conffrom 50M to 100M, allowing larger uploads via Nginx.MAX_FILE_SIZEinlenny/core/api.pyfrom 50MB to 100MB, permitting larger files to be processed by the API.Note
After Update make sure you update top Ngnix layer to support new changes on your Local machines or Cloud instance's or you might get blocked.