.supervisorconfig

[iangreenleaf]

I'd like to have a persistent config file. This should help the people who want a certain options always set a certain way, or who want to specify files to ignore, etc. Plus having the option of checking it into source control is nice.

I think the least confusing format will be just standard CLI arguments, like so:

--ignore src,vendor
-x nodespecial
--debug

Questions I'm pondering:

• We'll look for this file in the current working directory. Should we also look in home? Or look in every parent directory of CWD?
  • If two files exist, do we use the nearest? Or combine them with the nearest taking precedence?

See #48, #84.

[arxpoetica]

+1

[antsav]

+1

[ralyodio]

+1. i find i have to manually tell it to watch .json files which is kind of annoying having to remember the command line args everytime i start it.

[niftylettuce]

+1

[wuct]

+1, it will be really useful.

[tomdeboer]

Yes! +!

[djensen47]

It would be nice for supervisor to catch up to nodemon in this respect.

[DarkAxi0m]

What about passing a config file; kind of like supervisor -c supervisor.json ?

Edit: on that, it's nice how composer has composer.local.json (not stored in git) and composer.json (stored in git) so you can have overrides just for one instance.