Hello, we have a Django project with a few pages that come from Git. Currently, Apache rewrite rules serve those files statically (and they make use of the same template/CSS as Django does, so the user does not actually notice), and it's a massive hack and pain to keep up-to-date.
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. I've seen http://luispedro.org/software/git-cms, but that does way more than just sourcing from Git. And it's not immediately obvious to me how it even does the Git interaction. 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? Would it be hard to write? Where would one start? Thanks, -- @martinkrafft | http://madduck.net/ | http://two.sentenc.es/ mulutlitithtrhreeaadededd s siigngnatatuurere spamtraps: madduck.bo...@madduck.net -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/20141121222930.GA15206%40fishbowl.rw.madduck.net. For more options, visit https://groups.google.com/d/optout.
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
