From 0b4cff586c79dbf88c6c964f29d2cd584aa219c2 Mon Sep 17 00:00:00 2001 From: David Dollar Date: Tue, 8 Mar 2011 12:18:11 -0500 Subject: [PATCH] rebuilding man page --- index.html | 33 +++++++++++++++++++++++++++++---- 1 file changed, 29 insertions(+), 4 deletions(-) diff --git a/index.html b/index.html index da136f8..6bec8ae 100644 --- a/index.html +++ b/index.html @@ -66,9 +66,11 @@ EXPORTING OPTIONS EXPORT FORMATS + JSON EXPORT INITTAB EXPORT UPSTART EXPORT PROCFILE + DEFAULT OPTIONS EXAMPLES COPYRIGHT @@ -155,11 +157,19 @@ application.

foreman currently supports the following output formats:

+

JSON EXPORT

+ +

Will export your processes as JSON:

+ +
{ "web": { "command": "bundle exec thin start" } }
+
+

INITTAB EXPORT

Will export a chunk of inittab-compatible configuration:

@@ -186,8 +196,23 @@ will be structured to make the following commands valid:

A Procfile should contain both a name for the process and the command used to run it.

-
web:  bundle exec thin start
-job:  bundle exec rake jobs:work
+
web: bundle exec thin start
+job: bundle exec rake jobs:work
+
+ +

You can validate your Procfile format using the check command

+ +
$ foreman check
+
+ +

DEFAULT OPTIONS

+ +

If a .foreman file exists in the current directory, default options will +be read from it. This file should be in YAML format with the long option +name as keys. Example:

+ +
concurrency: alpha=0
+port: 15000
 

EXAMPLES

@@ -213,8 +238,8 @@ job: bundle exec rake jobs:work
    -
  1. Foreman 0.10.0
  2. -
  3. December 2010
  4. +
  5. Foreman 0.11.1
  6. +
  7. March 2011
  8. foreman(1)