Uploading images in project description fails about a4-product HOT 5 CLOSED

Works for me locally.

from a4-product.

the images are stored with the access permissions -rw------- (600) and are thus not readable by the user the nginx server is running.
@2e2a you reported this behavior before. did you find out why the permissions were set that way? and how did you resolve the problem on meinBerlin liqd/a4-meinberlin#581

i tried to reproduce, but the image i did upload now is stored with the correct permissions -rw-r--r-- (644) :(

from a4-product.

No, I could not reproduce it and it did not occur again.

from a4-product.

i fixed the uploaded images permission for now manually by running
find /home/django/django/media/uploads -type f -exec chmod 644 {} \+
from within the container. but this issue is really weird.

from a4-product.

the problem resulted from the django file storages behaviour in regard to temporary files.
if a file of a size less then 2.5mb was uploaded it is stored first in memory and finally, after validation, stored to the disk
for files greater then 2.5mb a concrete temporary file with the 600 perms is created for the uploaded data. this file is later renamed to the desired filename, but the perms are not adapted.
to explicitly set the perms to 644 the https://docs.djangoproject.com/en/2.0/ref/settings/#std:setting-FILE_UPLOAD_PERMISSIONS setting has to be set.
this issue is closed as the deployment has been extended set FILE_UPLOAD_PERMISSIONS = 0o644

from a4-product.