Posts by _alex

Nice.
Swagger doc would be a real plus, too.
I see this would be easy when going with apigility.org

Noticing the Announcement for the FrontEnd Rewrite, it would be great to see this built strictly on top of a REST-API that could be used for integrations into other Systems.

Hi Nuxwin,
thanks - hacked them pretty ugly what broke with every update but more worse messed-up things after i edited reseller-props limits of the reseller's domains were reset to defaults (this maybe is another topic / won't happen anymore when released).

Quote from Nuxwin

@_alex

The parameters set through the PHP Editor doesn't affect CLI SAPI. So yes, you're right about *shoud* vs *must* but nothing prevent you to set the upload_max_filesize to a low value. In the PHP editor, you can have

memory_limit: 32
post_max_size: 16
upload_max_filesize: 2

Thus, I don't really see the problem here...

Of course, I can remove the constraints but in that case, customer will have to pay attention.

Display More

Hi Laurent,

well, but what if it's the other way round ?

I want to accept files up to 200Mb in Size (PDF's, doing checks with poppler utils, create thumbnails with ghostcript and what not).

My php-app is fine with 64mb memory_limit,
so reasonable settings are:

memory_limit 64
post_max_size 200
upload_max_file_size 200

What happens is that i'm forced to set memory_limit > 200mb by imscp, what imho is absolutely not necessary ...

Other use-case would be collecting video-uploads with php, then process with ffmpeg.
Here it could end that memory_limit needs to be in the size of several gigabytes.
Just to move the files with move_uploaded_file somewhere a cron catches up for processing.

I appreciate the poll, but wouldn't a third option 'make it configurable if imscp forces them' make sense ?

btw., as memory consumed by gd is accounted into memory_limit these settings absolutely don't keep people from running out of memory / into memory_limit, even when processing uploaded images much smaller than memory_limit ...

IMHO it would be really at time to re-think the constraints of memory_limit, post_max_size and upload_max_filesize defined in PHPini.php

There is a comment saying "According PHP doc, post_max_size value *must* be lower than memory_limit value"

The truth is:
http://php.net/manual/en/ini.core.php#ini.post-max-size
"Generally speaking, memory_limit *should* be larger than post_max_size."

Notice the difference between *must* and *should*, good reading about is here
https://www.ietf.org/rfc/rfc2119.txt

There are enough cases where uploaded data is not processed by php, and there is no need to have a ridiculous high memory_limit just to accept large fileuploads.

i.e. upload of images that are processed via cli-tools and not within the http-request.