If I wanted maximum performance from a distributed on the fly template system. I'd probably store them in a fast document db.
On Wednesday, October 19, 2011 at 5:54 PM, Kurtis Mullins wrote: > Very true, I could definitely implement it as a pluggable loader. I'll try to > find the DB Template Loader too. I'm mainly concerned with this being a large > bottle neck for our front-facing pages so I'm not sure which path to choose. > Maybe some R&D is in order :) Thanks! > > On Wed, Oct 19, 2011 at 5:52 PM, Donald Stufft <donald.stu...@gmail.com > (mailto:donald.stu...@gmail.com)> wrote: > > The template system uses pluggable loaders that can locate a template based > > upon it's name. So using that you can store your template anywhere. There > > is already an app for storing templates in the db, you could easily make > > one to store it somewhere else as well. > > > > On Wednesday, October 19, 2011 at 5:48 PM, Kurtis wrote: > > > > > I'm working on a project where I will eventually need to be able to > > > add/delete/manage templates on the fly. Our Django Application Servers > > > are setup as a cluster behind an Nginx Front-end Server. > > > > > > We're not at that point, yet -- but I wanted to see if there's any > > > architectural issues I need to prepare for. I was thinking we could > > > store them on some sort of a networking file system but then I worry > > > about load-times and stability. We could store them in a database but > > > I imagine that may slow things down even more, plus we'd have to build > > > some sort of a system for pulling templates from the database. > > > > > > If anyone's attempted this sort of thing before, I'd be interested in > > > hearing some options you took and the outcome. > > > > > > Thanks > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Django users" group. > > > To post to this group, send email to django-users@googlegroups.com > > > (mailto:django-users@googlegroups.com). > > > To unsubscribe from this group, send email to > > > django-users+unsubscr...@googlegroups.com > > > (mailto:django-users+unsubscr...@googlegroups.com). > > > For more options, visit this group at > > > http://groups.google.com/group/django-users?hl=en. > > > > > > > > > > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-users@googlegroups.com > > (mailto:django-users@googlegroups.com). > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com > > (mailto:django-users%2bunsubscr...@googlegroups.com). > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com > (mailto:django-users@googlegroups.com). > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com > (mailto:django-users+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
