On 21 January 2013 17:54, Silvio Siefke <siefke_listen@web.de> wrote:>
> The socket is not present in /tmp. Whereis the mistake?

It looks like uWSGI hasn't created it. Perhaps you didn't run it in a
way such that it had permission to do so.
I'm afraid I can't help you troubleshoot that program and, just FYI,
this isn't the mailing list on which to do that.

> Is there no way to make the Vhost configuration so that it does not
> matter what the user is in? PHP, Perl or Python?

If your code/container can listen on a socket, and you know what
protocol it speaks, and can deterministically configure nginx to use
that protocol, then there's no reason why you can't abstract the nginx
config away from having per-app knowledge. I suggest that it's
probably more bother than it's worth, unless you have very specific
mass-hosting or NoOps requirements, however.

Jonathan
--
Jonathan Matthews // Oxford, London, UK
http://www.jpluscplusm.com/contact.html

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx