Small Branch from #594704: Allow packaged install profiles on d.o to pull in code from other sources + sites

One of the criteria we are considering for packaging external third-party libraries is file size limits.

Is this a concern for Drupal.org hosting? What size limit is reasonable? 2GB, 100mb...?

Comments

philbar’s picture

philbar commented
Issue tags: +packaged install profiles

tagging

pwolanin’s picture

pwolanin commented

I think something in the range of 10 MB per library (compressed) is a reasonable maximum.

Here are some examples of compressed libraries that I know are used by Drupal modules:

http://code.google.com/p/simplesamlphp/downloads/list : 1.4 MB
http://code.google.com/p/solr-php-client/downloads/list : 0.1 MB
http://aws.amazon.com/sdkforphp/ : 1.7 MB
http://download.cksource.com/CKEditor/CKEditor/CKEditor%203.4.2/ckeditor... : 1.9 MB
http://www.phplist.com/download : 3.3 MB

so none of these is even close to 10 MB.

gerhard killesreiter’s picture

gerhard killesreiter commented

Are we talking "per profile" or "in total"?

If "per profile":

I've difficulties to see what people would put into a 10GB profile...

I think Peter's 10MB make much more sense.

philbar’s picture

philbar commented
Status: Active » Fixed

This limit will be a limit whitelist maintainers will enforce. Theoretically, if a install profile developer wants to package a 1GB library, we need to know drupal.org can handle it.

10mb will work for over 90% of use cases. We can stick with 10mb compressed for the time being and if someone wants to include a larger library we can reopen this issue.

Status: Fixed » Closed (fixed)
Issue tags: -packaged install profiles

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +packaged install profiles

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.