We're a small organization with limited sysadmin support and a low thruput requirement.
I've got some common features that are evolving that are used in all projects, even though the projects themselves are unrelated and on different servers. I have a very specific logging function to a mysql DB (same server, different database) to comply with gov't regs. I've got a very specific security feature that queries some legacy code via HTTP and another MYSQL DB (again a separate database from the main application). I'm using django 1.5.1 and Python 2.6 on CentOs I would like to use the same code in various projects. Should I move these features into separate django applications and if so, how should I structure my directories and imports to keep it clean. I suppose this might be a candidate for middleware, but I'm the only guy working on this and cannot devote much time to "infrastructure tangents" no matter how good they might be. I would appreciate a little advice on the good, bad and ugly solutions to the above, based on the communities more extensive experience. Thanks, Fred. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
