config format for programs is very fragile

[mjpieters]

The current format requires that we specify each program on a single line with additional supervisord options in between (...) parenthesis in the 'right' location. The recipe parses these lines using a regex.

There are, however, several supervisord options for program sections that accept %(...)s variable substitutions, and those substitutions have ( and ) characters in them. The regex is not sophisticated enough to handle these, so any use of variables in supervisord options breaks the format.

Rather than cram everything into a single line, the format should really accept buildout section names; e.g.

[supervisor]
recipe = collective.recipe.supervisor
# ....
programs = program-foo program-bar

[shared-config]
stdout_logfile=%(here)s/log/%(program)s/stdout.log
stderr_logfile=%(here)s/log/%(program)s/stderr.log

[program-foo]
<=shared-config
priority=10
name=foo

[program-bar]
<=shared-config
priority=20
name=bar

The parser would split the programs section by whitespace to then load each program configuration from buildout[sectionname] (validating that certain required keys are present).

This would make it much more flexible and powerful, the above example uses a shared section that is pulled into each program section to avoid repetition.

A short-term solution would be to at least fix the regex pattern to allow for %(\w+)s values inside the (... opts ...) section.