Open danielballan opened 3 years ago
My interpretation of the evidence is that we wanted to save working supervisor configurations that we were using during development, and that we were not skillful supervisor users (I still am not skillful). I don't think we need to keep these files anymore, but @gwbischof may feel differently. Also, the mongo_consumer code is slated to move to a different repository.
Personally I am happy to move from supervisor to systemd, but I think we can just remove the supervisor configuration files entirely from this repository without replacing them with equivalent systemd files.
Reviewing https://github.com/bluesky/bluesky-kafka/commit/a0c9e2b99aefdb19767433fde3923d3275db1f13#diff-8eedc134d422e0ea27511b9854a9911105811b0baecc17dd98554b01f095c3e7
[program:...]
block that should be placed in.../conf.d
(where...
varied by platform / how supervisor was installed). But these files are namedsupervisord.conf
andsupervisorctl.conf
and seem to configure supervisor itself as well as the bluesky-kafka consumer program. I'm not familiar with some of the directives and the commit message is not specific, so I can't tell what it's doing. Can you @jklynch or @gwbischof comment on what these are doing?supervisor
directory should be lifted into the root directory of the repo, outside of the Python package distribution.