Ptone: Coldbrew already uses a templatetag for development, but for
production, we want people to be able to have the collectstatic experience
and simple find collected coffee as compiled JS in their static directories.

As you suggest, I have reluctance about Bruno's solution.  Also, I'd be
concerned about the message sent to future generations by amending the docs
to read, "ensure that 'coldbrew' appears after 'staticfiles' in your
INSTALLED_APPS tuple."

Wrapping collectstatic is an enormously simple and elegant solution - to my
knowledge, this hadn't even crossed our minds at slashRoot.

Janis: I hadn't noticed that we can obtain a list of collected paths from
post_process - this is wonderful!  This seems like a winning solution at
least for obtaining a list of directories in which we need to search for
unbrewed coffee.  Come to think of it - is this the best way to do this?
Or is there a STATICFILES_STORAGE agnostic way of obtaining an
authoritative list of staticfiles locations?

My only concern is that we'll limit our audience by requiring users to use
a specific STATICFILES_STORAGE.  What if they're already using a custom one?




On Mon, Nov 12, 2012 at 3:08 PM, Jannis Leidel <lei...@gmail.com> wrote:

>
> On 11.11.2012, at 17:09, Justin Holmes <jus...@justinholmes.com> wrote:
>
> > My sense is that there are a growing number of use cases, but the one
> that I currently have in mind is for django-coldbrew.      I want to be
> able to compile all the coffeescript in a project during the collectstatic
> process.  Currently, we have a management command, "collect_coldbrew" - but
> I'd like to allow users to have this occur automatically during
> collectstatic.
>
> The collectstatic command calls a method "post_process" method [1] of the
> staticfiles storage if it exists and passes a list of file paths that have
> been collected [2].
>
> In other words, hooking into collectstatic is as easy as writing an own
> subclass of StaticFilesStorage (or whatever storage backend you've set
> STATICFILES_STORAGE) and implement the method.
>
> Would that suffice for your use case?
>
> Jannis
>
> 1:
> https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#django.contrib.staticfiles.storage.StaticFilesStorage.post_process
> 2:
> https://github.com/django/django/blob/master/django/contrib/staticfiles/management/commands/collectstatic.py#L116-127
>
> > I'm not sure if the best timing for the signal is at the end of the
> complete collectstatic process or at the end of each iteration (ie, one
> signal for each static directory that django finds).
> >
> >
> > On Sun, Nov 11, 2012 at 4:55 AM, Alex Gaynor <alex.gay...@gmail.com>
> wrote:
> > What's the use case?
> >
> > Alex
> >
> >
> > On Sat, Nov 10, 2012 at 8:48 PM, Justin Holmes <jus...@justinholmes.com>
> wrote:
> > Currently, our only built-in management signal is post-syncdb.
> >
> > I propose (and, notwithstanding objection, will build)
> post-collectstatic.
> >
> > Is this reasonable?  Is there another, less invasive way to hook logic
> into collectstatic?
> >
> >
> > --
> > Justin Holmes
> > Chief Chocobo Breeder, slashRoot
> >
> > slashRoot: Coffee House and Tech Dojo
> > New Paltz, NY 12561
> > 845.633.8330
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django developers" group.
> > To post to this group, send email to django-developers@googlegroups.com.
> > To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
> >
> >
> >
> > --
> > "I disapprove of what you say, but I will defend to the death your right
> to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
> > "The people's good is the highest law." -- Cicero
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django developers" group.
> > To post to this group, send email to django-developers@googlegroups.com.
> > To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
> >
> >
> >
> > --
> > Justin Holmes
> > Chief Chocobo Breeder, slashRoot
> >
> > slashRoot: Coffee House and Tech Dojo
> > New Paltz, NY 12561
> > 845.633.8330
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django developers" group.
> > To post to this group, send email to django-developers@googlegroups.com.
> > To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>


-- 
Justin Holmes
Chief Chocobo Breeder, slashRoot

slashRoot: Coffee House and Tech Dojo
New Paltz, NY 12561
845.633.8330

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to