On Tue, Aug 25, 2009 at 8:40 PM, Ryan Headley<[email protected]> wrote:
> Basically, I have a large client that wants several store fronts all managed > from one Satchmo instance. > [...] > my thought was that > I would start another app called "StoreB" that would have its own custom > products (again extending from Satchmo's product model). Where I am running > into confusing is that StoreA will need a completely different set of > customized templates than StoreB -- this is what I can't figure out. That's what site-skins does! It is very easy. You just make a "skin directory" and put it in your settings.py file. Each top-level directory in there is a "skin", which can be assigned to sites. The template loader figures out which skin to use for each request, and puts it at the top of the search order for templates. > I "could" kick off a process for each store and specify a different settings > file for each "app" that only overwrites SITE_ID and TEMPLATE_DIRS, but that > seems like it may not be the best way to go. I've tackled that before using > mod_python and a telling it a different settings file for each instance, but > is that the best approach? No, I don't think so. I've also run into problems with mod_python "leaking" memory between instances. If you go that way - with separate settings files, you should definitely use fastcgi or mod_wsgi and a standalone daemon for each store. -- Bruce Kroeze http://www.ecomsmith.com It's time to hammer your site into shape. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
