If we're going to unzip and rezip then what's the value in saving the
pre-multimedia zip in the first place? (Instead of just zipping every
just-in-time)?


On Wed, May 14, 2014 at 12:32 PM, Daniel Roberts
<notifications@github.com>wrote:

> In corehq/apps/app_manager/urls.py:
>
> >      url(r'^download/(?P<app_id>[\w-]+)/',
> >          include('corehq.apps.app_manager.download_urls')),
> > +    url(r'^download/(?P<app_id>[\w-]+)/(?P<path>.*)$', 'download_file',
> > +        name='app_download_file'),
>
> This hits upon an issue that's specific to this file; normally we save all
> files directly to the app build so that when they're accessed later we know
> we always get the same file, even if the commcare-hq code has changed in
> the meantime. That's impractical for this case because we're going to be
> zipping all multimedia into the file, which would be really expensive
> storage wise.
>
> I think the best solution is to save the file pre-multimedia zip like we
> do with other artifacts, and then unzip and add multimedia just-in-time.
> You can grab me to discuss, I think I have a pretty good idea of how to do
> that.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/dimagi/commcare-hq/pull/3410/files#r12646067>
> .
>