Develop one supervisord configuration that supports running under either apache or runserver

[kerchner]

#225 encountered difficulties developing a supervisord configuration for SFM that supports running under either apache (as www-root) or runserver (as "my user") without resorting to creating the supervisor socket file with 777 permissions.

To recap the note in #225, here's what didn't work:

• add "my user" to the www-root group
• configure /etc/supervisor/supervisor.conf to create supervisor.sock with chown=www-root:www-root and with chmod=770

We expected that running sfm as "my user" with runserver would be able to call supervisor (via actions such as enabling/adding a twitterfilter, disabling/deleting a twitterfilter). However, it results in a permission denied error. Because this error is resolved by setting supervisor.sock to 777 (or ownership to my user), we can presume it's some sort of permission issue. The purpose of this ticket is to further investigate that issue and bring it to resolution.

[kerchner]

And don't forget to adjust the permissions on /var/log/sfm accordingly - once myuser is a member of www-data, /var/log/sfm can be tightened up to 770.