Hi there, I'm an experienced developer, but new to Django. I've experimented with Django over the years, but I'm now in the process of planning a medium sized Django app. We have an in-house support/email system written in python, but it needs an overhaul. :)
The application will become a simple CRM system, with the following pieces: * Email ticket tracking * Simple Customer database * Possible integration with order/licensing systems, etc. * Some parts of the app will also have command-line scripts to handle the integration with mail queues. So it's not a purely web-based app. I'd love some advice on structuring a project like this. In particular the structure of applications/packages within the project. Django seems to encourage the creation of reusable "applications". When building a system like this, how does this apply? Do you simply create a "project" with a single "application"? If so, then you end up with python package names like "mysite.myapp", which seems kind of redundant in this case. Is there a recommended best-practice approach to this type of project? Or maybe even point me at a project that I can use as an example. Would there be any benefit of separating a system like this into separate django "applications"? PS: Whenever I've looked at Django ... I've found myself confused about the concept of apps vs projects. What am I missing? Maybe after developing with Django for a while it will all become clear. :) Thanks, Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
