'runserver' is largely intended for 1) Being able to run tests on your dev box before committing to test or production. 2) Being able to take a laptop and ethernet switch to a customer's site and provide a working demo.
Unless you are heavily invested in Apache, or have a glut of unemployed Apache experts that actually know more than "Put HTML files in /var/www", skip Apache and go with lighttpd or nginx. I was quite unhappy with the amount of fiddling required to get Apache to play nice with PHP and Django sites once i replaced mod_php/mod_python with mod_fastcgi and switched to an offshoot of Apache my employer maintains and ships to customers. After doing similar work for another job, I found lighttpd and nginx easier to configure for the same result, although I didn't find the documentation for either as pleasant to read as Apache's. Go ahead and invest the time to get your test environment as similar as possible to your production environment. Make plans on managing staticfiles sanely. http://docs.djangoproject.com/en/dev/howto/static-files/ is good reading and i recommend making use of django-staticfiles until django 1.3's django.contrib.staticfiles is released. On Jan 25, 2:23 pm, Allan Stavely <[email protected]> wrote: > Thanks for the suggestions, folks. Yes, I should explain... > > My intention was to run a site in a sort of beta-test mode, where it > would do real work but with very low volume -- only a few select users > would know how to connect to it. I was hoping to be able to deal with > Apache (or whatever) once everything else was sorted out. > > Or is this a silly idea? > > - Allan > > On Tue, 25 Jan 2011, Peter Halliday wrote: > > Is this for development? Because if this was for production I'd say you > > shouldn't do that. Instead you should just run apache + mod_wsgi or some > > other deployment method. > > > Peter Halliday > > Excelsior Systems > > (Phone:) 607-438-2527 x101 > > (Fax:) 888-265-5082 > > > On Tue, Jan 25, 2011 at 10:50 AM, allan <[email protected]> wrote: > > >> Hello all, > > >> I'm in the process of deploying Satchmo on a Linux (CentOS) virtual > >> machine. I'd like to install a daemon to start Satcho (e.g., "python > >> manage.py runserver") on boot, manage starting and stopping it, and so > >> on. The daemon will live in /etc/init.d/ and follow the protocols for > >> daemons that live there. > > >> It looks like a routine job, but has anyone else written one so I > >> won't need to do it myself? > > >> Thanks! > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Satchmo users" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]<satchmo-users%[email protected]> > >> . > >> For more options, visit this group at > >>http://groups.google.com/group/satchmo-users?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Satchmo 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 > > athttp://groups.google.com/group/satchmo-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Satchmo 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/satchmo-users?hl=en.
