Serving static files separately

[Piet Delport]

In some deployment scenarios, it is desirable to collect and serve static files separately from the web application processes running Fanstatic.

For example, Django's staticfiles framework provides a collectstatic command, which collects all the static files used by a Django instance into an output directory, which may be served by a separate static file server (which the Django instance is configured to point static file references to).

Are there plans to support something like this in core Fanstatic?

I found the rebecca.fanstatic package, which provides a list_fanstatic command, but it would probably take more elbow grease to really make such a setup work, at the moment.

[Jan-Jaap Driessen]

Hi Piet,

I had a look at rebecca.fanstatic, my guess is this is how a 'static
collector' in fanstatic would work.
What would you need to change in rebecca.fanstatic in order to make
this work in your setup?

There are some ideas on making fanstatic more lightweight, for
instance splitting of the publisher into a separate package. Perhaps
this package could be the location of the 'static collector' script.


Cheers,

JJ