celery workers aren't started (digital ocean)

[jean]

The playbook as is ends up with a system that doesn't run any workers. It also isn't configured to run workers: it tries to run celery workers as root. This fails.

(ve) root@sentry:~# sentry --config=/var/sentry/sentry_conf.py celery worker
Running a worker with superuser privileges when the
worker accepts messages serialized with pickle is a very bad idea!

To fix this, a celery worker user needs to be created, and the supervisord config needs to be changed to launch workers as this user.

I'm not sure how this should work exactly, as I'm not familiar with celery (what permissions does this worker user need, what does it connect to?), but I'll try to figure it out.