Could you regard a file size of downloaded nextcloud-zip-file for web updater below 256MB by easiest-way increasing compression level?
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
Hello Nextcloud - developers,
our webhosting allows 256M php memory limit and I know that you recommend 512M and I read the red-colored hint in admin overview console.
But we don't overdo its usage and for our purpose it runs fine with 256M.
Unfortunately starting with v31 it seems to be exactly at the limit:
When I use LZMA ultra compression level in 7-zip it's easy to come down to 225MB.
Could you regard this on your next releases as a very simple way to be able to use web updater on upcoming version on 256M php memory limit webservers?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the web updater obtains and validates the Nextcloud ZIP archive, then identify where release archives are produced and compressed. Verify that a more highly compressed archive stays below 256 MB and that the updater still completes within a 256 MB PHP memory limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100