I tried to upload a video file for a bug which is about 14MB size, it showed an error message while trying to upload.The file size limit should be increased for tasks because often times the video shots for the bugs are of usually around this size.
|Invalid||• chasemp||T34 Configure Phabricator for our needs|
|Resolved||• chasemp||T160 Configure the size limit of the file upload configuration for tasks to a higher limit than 10MB|
qgil wrote on 2014-05-01 17:41:18 (UTC)
Alright, so this is the document explaining what needs to be done.
Someone with the permissions might want to try, or we can wait until we have an official instance.
qgil wrote on 2014-05-13 19:28:22 (UTC)
See T322: Possibility to pair API documentation with user comments, where one of the Phabricator maintainers says that handling files above say 16MB might be problematic.
aklapper wrote on 2014-05-30 14:32:49 (UTC)
@Ryasmeen: Are there examples for "usually around this size"?
Would love to base this decision on some more input, because currently I'd propose setting a maximum file size of 15MB is sufficient (so we'd stay under 16MB for performance reasons)? If videos are larger, are explanations in https://commons.wikimedia.org/wiki/Help:Converting_video sufficient how to shrink their size?
I only see videos getting to such large size; if I miss other file types, please tell.
aklapper wrote on 2014-06-12 19:50:56 (UTC)
We currently think of sticking with Bugzilla's currently allowed file attachment size (10MB) as we don't want to create a regression but don't plan to do a whole lot of performance testing due to a higher file size either.
Still, @mmodell plans of doing some testing when it comes to file storage.
For files larger than 10MB to link to from tickets, existing workarounds (upload to a wiki, server, youtube) might have to stay around for a while. :-/
Also, can we make it 35MB, so I can upload the release .tar file that our scripts spit out? External linking will not work, since these need to stay private to the security team and people we give early access to.
I'm not sure how bad performance would be but I suspect that it would be pretty terrible. This is a fairly well educated guess; I worked on the file serving code as part of making private files really private. By implementing extra checks, we made phabricator file serving quite a bit less efficient, as a direct consequence of wikimedia security requirements.