Spawning applications based on a directory of config files

[mattrobenolt]

Proposing this would allow a more traditional deployment method with a "sites-available".

I envision a command such as forever vhosts /etc/forever/sites-available and the directory would contain a set of *.json config files.

Each config would be structured similar to:

{
  "script": "/var/www/app.js",
  "accessLog": "/var/log/my-app/access.log",
  "errorLog": "/var/log/my-app/access.log",
  "options": {
    "max": 3
  }
}

All of these options would be passed along right to a start command, simulating a bunch of forever start ... commands.

Also: I'm willing to develop the feature myself, I just want to make sure it's done in a way that is in line with the rest of the project.

[indexzero]

Lets start small. I would first envision this as a .forever file (with the format you've described) in the current directory one could simply:

  $ forever start
  Using settings in /path/to/pwd/.forever
  {
    "script": "/var/www/app.js",
    "accessLog": "/var/log/my-app/access.log",
    "errorLog": "/var/log/my-app/access.log",
    "options": {
      "max": 3
    }
  }

From there we can talk about directories of these files. Start small, incremental improvement

[mattrobenolt]

No problem. I'll fork the repo and take a stab at this today.

[mattrobenolt]

@indexzero Very simple, just pass along EVERYTHING through options just like it's specified in the actual API. The only required field is "script" inside the .forever file. This could very easily work to spin up a directory of files without an issue.

[mattrobenolt]

Bump.

[tglines]

+1

[alexbhr]

+1

[Guuz]

This sounds like a good idea. Right now i have a start.sh script with the (long) forever start command with all the needed parameters for logfiles etc. It would be better if you could start your applicatie through forever in combination with a options file.

I also set the PORT and NODE_ENV enviroment variables.

[indexzero]

Fixed in #733 and #737