I like Simon's ideas about shared location and separate app (Django encourages us to use apps to share anything), but you also may share them on VCS level. SVN supports "external" checkout, in git you may add one repository to another.
\project1\templates\shared_temps \project2\templates\shared_temps "shared_temps" in both cases is just a repository (folder with .git subfolder). So, you commit in one folder, push, and pull in all other projects. On Friday, March 6, 2015 at 5:24:04 AM UTC+3, JHeasly wrote: > > Hello — > > I'm looking for any blogposts/best practices for deploying a common set of > templates across multiple Django projects. > > My initial impulse is to just make a master Github repo of the template > and pull it into each of the projects. Are there better approaches? > > TIA, > John > -- 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/9884c3d6-9bc6-4b87-95ef-b4fbbd28f793%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
