I'm building a tool for a client that synchs email addresses between systems and decided to use the excellent django framework because it gives me a quick and powerful connection to a database back-end and the ability to provide a web front-end for the users. I'm trying to decide if it's worth going through the trouble of setting up Apache to serve the program or if I can safely get away with using django's server. Here are the details.
This program will reside on an in-house server and will not be accessible by the public. There will only be one user at a time. The program will likely run once or twice a day, at which point it will do some light interaction with MySQL. It will also be available at all times to staff via their web browser (and an internal IP address) should they wish to check a log of previous transactions. My instincts tell me I can get away with using the test server, as what I'm doing is hardly a web application that needs to deal with thousands of transactions. I imagine I could just set up a startup script in OS X to launch the django server at startup and leave it running. Any advice -- either saying yes this is a good idea or no there are serious drawbacks to this approach -- greatly appreciated! Cheers, Kevin --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
