On Jul 12, 2006, at 4:11 PM, Iván Alemán wrote: > I mean that actually we're using LAMP environment plus other goodies > like Dojo, so the refined question (hopefully) is, can I integrate any > django project to my actual PHP/MySQL environment with minimum effort > so later (after publishing) we can start worrying about moving > everything to Django or is better to build everything on Django due > our inexperience ;)
It shouldn't be *too* hard to integrate the two, but do keep in mind that some people have reported bugs running both mod_python and mod_php in the same Apache process (more info here: http:// www.djangoproject.com/documentation/modpython/#if-you-get-a- segmentation-fault). I'd recommend a seperate process, and at that point you would easily be able to run both at once (against the same database, even). > What I mean is if its possible to integrate easily Django to an > on-going production project which is been developed heavily under > PHP/MySQL? Ah -- I see. You should take a look at the information about how to integrate Django with a pre-existing database: http:// www.djangoproject.com/documentation/legacy_databases/ > Yes, our project is about social networking, so it's very important > for us to set the foundations for a permission granularity in many > aspects on the site e.g. an user can do anything meanwhile "anything" > belongs to him (with "anything" I mean blogs, forums, communities, > profile, etc.) and also an individual can be part of a blog or a > community and have some permissions or also be part of the staff group > of a particular group, I want that my users have control of their own > groups (group management), and I want to have control of their > accounts like disabling / enabling / reviewing accounts. Of course that's totally possible. You don't get that for free from Django, but the auth framework is pretty nice and should make that stuff pretty painless (I'd hope). > Another aspect in which I am curious is the sessions handling, in PHP > for example you can detect whether an user is online or not and have > one session per user, not allowing login attempts with the account > that is already in use. I feel that this is possible using Django > right? This doesn't sound hard. Now, I've not done anything like it myself -- I use at least two computers on a daily basis, so this type of check annoys the hell out of me -- but I doubt it would be more than a couple of lines of code. Probably a middleware component would be your best bet here. > I am also dealing with the templates, meanwhile here our designers are > used to Smarty, and what I saw from the tutorial it's something indeed > different in many ways to set the look and feel, but of course not > impossible :) Smarty was one of the sources of inspiration for Django's template language, so I'd expect someone who "gets" Smarty to pick up Django's templates pretty quick. Later, Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
