Very pleased to hear it; thanks for reporting back!
--Stuart On Fri, Jan 28, 2011 at 4:35 PM, Allan Stavely <[email protected]> wrote: > > Many thanks, Stuart! Once I reconsidered, I agreed with this advice > entirely. > > I ended up using nginx and fastcgi. I found I couldn't use gunicorn because > of issues on my site (mostly an ancient Python, and dire warnings that I > would break important things if I upgraded). > > Even with some false starts, it only took me about one full day, and I had > never done anything like this before. > > And it runs! > > Cheers, > > - Allan > > > On Tue, 25 Jan 2011, Stuart Laughlin wrote: > >> Not all that silly, but I reckon that by the time you mess about with >> the scripts for init.d etc., you could have had it running in a >> 'proper' production-like scenario. Puts a bit more work up front, >> perhaps, but I think it would be worthwhile to bite the bullet early >> and do this sooner rather than later. I knew virtually nothing about >> nginx / gunicorn / supervisord (I'd always done apache/mod_wsgi) yet I >> was able to work though that article by Bradon Konkle in a relaxed >> morning. >> >> Just my two cents. >> >> >> --Stuart >> >> On Tue, Jan 25, 2011 at 1: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]. > 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 at http://groups.google.com/group/satchmo-users?hl=en.
