>Hence I was thinking: how much trouble would it be to have Django >reach into Git rather than its database and obtain data there to be >filled into template slots? Ideally, there'd be the possibility of >running a filter (e.g. reStructuredText) between Git and the >template rendering.
>What I envision is a storage layer (with optional caching) that >either fetches from the filesystem (with a Git checkout, using mtime >for cache expiration), or directly from a local Git repo (using >either commit or blob hash for cache expiration). >Does anyone know of such a module? Yes: >Would it be hard to write? Where would one start? For examples of projects that do similar things: A git-backed wiki: -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7de0a097-ac9b-4231-86c0-e242c36a88cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
