Improve socket handling about isso

[posativ]

A much better way: use a "real" WSGI server that supports the things you mentioned out-of-the-box such as gunicorn or uWSGI (well, I know the latter is fairly old in Wheezy and does not work with Isso as I use a different caching API).

I am afraid of implementing chmod and privilege drop in Isso which is something I never did before (and thus unlikely to implement it right on first try) and other WSGI servers have already implemented. The initial socket support for unix domain sockets for the development server shipped with Python/${webframework i use} is, after all, maybe a bad choice as it encourages to use the internal development server instead of a real, fast, secure and lightweight WSGI server.

If you still want to use the internal server, you can use sockets in the /tmp directory (which I do with uWSGI (although it supports chmod etc.)) or bind on localhost:1234.

[posativ]

An example call for Gunicorn:

$ export ISSO_SETTINGS="/path/to/isso.cfg"
$ gunicorn -b unix:foo.sock -m 0666 -u user -g group --preload isso.run

[jgraichen]

Ok, thanks. I'll try to update my debian package to depend on gunicorn and update the init scripts to use gunicorn.

Are there any version constraints for gunicorn you are aware of?

[posativ]

Are there any version constraints for gunicorn you are aware of?

I tested with the version available in Wheezy (0.14.5).

[jgraichen]

Ok, thanks.

[jgraichen]

Just out of curiosity: Why not using gunicorn as an optional dependency for the "internal" server?

[posativ]

In case of debian packaging, I wouldn't mind if it is a required dependency because of a more flexible setup.