django-jackfrost 0.4.0

Selecting renderers

Add a JACKFROST_RENDERERS setting, which should be a list or tuple of dotted paths to python classes or functions, much like MIDDLEWARE_CLASSES, TEMPLATE_CONTEXT_PROCESSORS etc:

JACKFROST_RENDERERS = (
    'myapp.renderers.MyModelRenderer',
    'my_other_app.utils.SomeOtherRenderer',
)

In theory, I don’t care whether your JACKFROST_RENDERERS are functions or classes; if it’s a class it must implement __call__. Either way, it should, when called, return a number of URL paths to be consumed.

Renderers for models

If you have a model which has a get_absolute_url method, your renderer can be as simple as:

from jackfrost.models import ModelRenderer

class MyModelRenderer(ModelRenderer):
    def get_model(self):
        return MyModel

If you need to customise the queryset, there is a get_queryset method which can be replaced. There is also a get_urls method, if you need to go totally off-reservation.

Reading from sitemaps

Giving jackfrost the dotted path to a standard Django sitemap as one of the JACKFROST_RENDERERS should do the right thing, and get the URLs out of the sitemap itself without you needing to do anything or write a new renderer.

Reading from django-medusa

In theory, giving jackfrost the dotted path to a subclass of the django-medusa BaseStaticSiteRenderer should do the right thing, and get the URLs out of the medusa renderer itself, without you doing anything. It will avoid going through the medusa rendering process, instead it’ll go through mine.

Reading from Django RSS Feeds

Giving jackfrost the dotted path to a subclass of a Feed should do the right thing, and get the URLs out by asking the Feed for the item_link for everything in items, without you doing anything.

Writing a renderer

The most basic renderer would be:

def myrenderer_yielding():
    yield reverse('app:name')

or:

def myrenderer():
    return [reverse('app:name')]

Renderers may also be classes:

class MyRenderer(object):
    __slots__ = ()

    def __init__(self):
        pass

    def __call__(self):
        yield reverse('app:name')

Listening for renders

There are 8 signals in total:

• build_started is fired when the management command is run.

• reader_started is fired when a URLReader instance begins working.

• read_page is fired when a URLReader successfully gets a URL’s content.

• reader_finished is fired when a URLReader instance completes.

• writer_started is fired when a URLWriter instance begins working.

• write_page is fired just after the content is written to the storage backend.

• writer_finished is fired when the URLWriter completes

• build_finished fires at the end of the management command.

Rendering on model change

Additionally, there is a listener, jackfrost.utils.build_page_for_obj which is suitable for being used as a pre_save or post_save receiver for a Model instance, and will attempt to build just the get_absolute_url for that object.

Defining when a model may build

If a Model instance implements a jackfrost_can_build method, this is checked before building the static page. If jackfrost_can_build returns False, the page won’t get built. Any other value will result in it being built.

Defining different URLs

If a Model instance implements a jackfrost_urls method, this is used instead of the get_absolute_url, and should return an iterable of all the URLs to consider building.

If the Model instance has a get_list_url method, that page will also be built. Useful for updating any ListView pages, etc.

0.4.0

• Added signals.write_page which is fired after the storage backend has written the content.

• Added utils.eventlog_write for using pinax.eventlog and the aforementioned write_page signal to track built items.

• Added a ModelAdmin action for building a selection of model instances into their static counterparts, from the admin changelist.

• Made the receiver utils.build_page_for_obj actually work.

• the models module will be compiled using Cython, if installed.

0.3.0

• Replaced jackfrost_absolute_url method in ModelRenderer with jackfrost_urls, which allows models to add every URL they want to cause to be visited.

0.2.1

• Added support for Django 1.6

• Added celery tasks for building both a single URL, and all URLs.

0.2.0

• Initial release.