Thanks to Bruce Wade who suggested going all command line. In an init file with an args variable it is no problem to have a very long list of args.
Roberto: I used pip to install v 1.2.3. Would it have included xml support by default? I had previously downloaded the package for xml but perhaps the default build doesn't include it. I am not in love with xml. It is what all the cookbooks and nearly every web site showed (for example, most of the django guys write up uwsgi using xml config files). I'd be perfectly happy with json or ini style config files. Is support for both "built in?" I had read the doc on the options but sometimes the short form is not mentioned. I'd agree that it makes sense to use long form. In answer to one of your earlier questions--yes, the options and the way uwsgi works is logical. It is very functional. The problem comes when some fundamental prereq is left out during the build or install (if retrieving some very out of date version from a repository). Then, it becomes very difficult to diagnose what is going wrong. As (very) frustrating as it was I am happy with the change. Dozens of lines of apache config are replaced by less than a dozen lines for nginx. Enough with admin for a while. Back to design and coding--the fun stuff. Case closed. On Friday, May 18, 2012 10:37:48 PM UTC-7, Roberto De Ioris wrote: > > > > Well, I revised my init.d script to work. > > > > Config files do not work at all in any way, shape or form. Just broken > > utterly. > > > > It turns out even loading simple startup variables to the init script > does > > not work. Period. > > > > It would appear that for some reason the only way uwsgi works is with > > command line arguments, many of which aren't documented. For example, > > everyone uses -M. I did a search for it in the wiki. Many examples > > include it. The global listing of (not) all arguments does not show it. > > What is it? > > > > I am on a linode vps running ubuntu 11.10. The only person who logs on > is > > me to do config horrors. I log on as root. So, the commmand line to > start > > uwsgi is run as root. As a command line, it works. When it references > > any > > external config file it does not work. Should I file a ticket, Roberto? > > You'll say you can't reproduce. But, I can't reproduce it ever > working > > at all. So, I have wasted 20 hours attempting to debug config files > that > > are inherently unusable. > > Run > > uwsgi --help > > for the full list of options (and their shortcuts). I suggest you to not > use shortcuts, as you will forget what they mean soon. Use long format. > > -M --> --master > > Regarding config files, read here how they works: > > http://projects.unbit.it/uwsgi/wiki/Doc > > (you do not need to read it all, just the first part). > > Try that (call it foo.ini) > > [uwsgi] > http = :8080 > master = true > > Then > > uwsgi --ini foo.ini > > Go to your browser to port 8080, it will work for sure. > > I suspect you are trying with xml files, but without xml support. > If you really love xml format, be sure to have installed libxml2-dev as > described here: > > http://projects.unbit.it/uwsgi/wiki/Install > > and rebuild uWSGI. > > Finally, you are on Ubuntu, throw away those ancient init scripts and use > what Ubuntu wants: upstart scripts > > http://projects.unbit.it/uwsgi/wiki/Upstart > > Obviously the previous link does not show you how upstart works, but you > can find more complete docs on ubuntu site (it is a lot easier than init > scripts and Ubuntu will not move to SystemD, so you'd better to invest a > bit of time in it). > > Another important link is that one: > > http://projects.unbit.it/uwsgi/wiki/ThingsToKnow > > I think you have all the pieces. > > -- > Roberto De Ioris > http://unbit.it >
