Guys, I'm trying to lay out Django code for large "website", which consists of four subsytems: - employees' website - statistics website used also by employees - public website (with users accounts) - monitoring webservices
This four components have different: - auth types, - different user types (employee account has really nothing to do with customer account) - different permission system - different webpage layout, css, media - different forms What is common between them: - they use the same database - most of models are shared between - global configuration (database uri, debug level, i18n, session etc.) In (for example) Zend Framework it's very easy to lay out: every subsystem is one ZF module and authentication is delegated to appropriate plugin based on detected module. Every module has its own controllers (Django views) + helpers, templates etc. Models connected with specific module are stored within module directory, and "global" models are available for all ZF modules. All rocks in a minute, code has very readable structure. Can Django handle such modular code layout? What's your advice? Cheers, Piotrek -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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=.
