qcluster 启动方式改为supervisor启动, 增加稳定性

[LeoQuote]

关联issue
#242
#224
#188
#211
#218

[codecov]

Codecov Report

Merging #230 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #230   +/-   ##
=======================================
  Coverage   82.16%   82.16%           
=======================================
  Files          64       64           
  Lines        7964     7964           
=======================================
  Hits         6544     6544           
  Misses       1420     1420

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e09dd4e...521d5d6. Read the comment docs.

[hhyo]

debug.sh文件也改下？

[LeoQuote]

不用吧，都debug了就直接运行呗 发自我的 iPhone

…

在 2019年5月28日，18:52，小圈圈 ***@***.***> 写道： @hhyo requested changes on this pull request. debug.sh文件也改下？ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[hhyo]

通过docker-compose 启动，无法控制启动顺序，有可能Archery服务启动qcluster时redis还没有启动，会导致qcluster启动失败，但是qcluster不会去重试Koed00/django-q#223
进程也不退出，就会有个假的进程在

[2019-06-01 09:37:42,726][MainThread:4656580032][task_id:django-q][cluster.py:53][INFO]- Q Cluster-18154 starting.
[2019-06-01 09:37:42,751][MainThread:4656580032][task_id:django-q][redis_broker.py:37][ERROR]- Can not connect to Redis server.

supervisor也只是解决了重启的问提，初次启动这个坑还在

[LeoQuote]

可以考虑使用docker -compose的功能
depends_on:
- db