spawning(1)

1SPAWNING(1)                      User Commands                     SPAWNING(1)
2
3
4

NAME

6       spawning - manual page for spawning 0.9.5
7

SYNOPSIS

9       spawning [options]
10

DESCRIPTION

12       Spawning is an easy-to-use and flexible wsgi server. It supports grace‐
13       ful restarting so that your site  finishes  serving  any  old  requests
14       while  starting new processes to handle new requests with the new code.
15       For the simplest usage, simply pass the dotted path to your wsgi appli‐
16       cation: 'spawn my_module.my_wsgi_app'
17

OPTIONS

19       --version
20              show program's version number and exit
21
22       -h, --help
23              show this help message and exit
24
25       -v, --verbose
26              Display  verbose  configuration  information when starting up or
27              restarting.
28
29       -f FACTORY, --factory=FACTORY
30              Dotted path (eg mypackage.mymodule.myfunc) to a  callable  which
31              takes  a  dictionary  containing  the command line arguments and
32              figures out what needs to be done to start the wsgi application.
33              Current  valid values are: spawning.wsgi_factory.config_factory,
34              spawning.paste_factory.config_factory, and  spawning.django_fac‐
35              tory.config_factory.   The  factory  used  determines  what  the
36              required positional command line  arguments  will  be.  See  the
37              spawning.wsgi_factory module for documentation on how to write a
38              new factory.
39
40       -i HOST, --host=HOST
41              The local ip address to bind.
42
43       -p PORT, --port=PORT
44              The local port address to bind.
45
46       -s PROCESSES, --processes=PROCESSES
47              The number of unix processes to start to use  for  handling  web
48              i/o.
49
50       -t THREADS, --threads=THREADS
51              The number of posix threads to use for handling web requests. If
52              threads is 0, do not use  threads  but  instead  use  eventlet's
53              cooperative   greenlet-based  microthreads,  monkeypatching  the
54              socket and pipe operations which  normally  block  to  cooperate
55              instead.   Note that most blocking database api modules will not
56              automatically cooperate.
57
58       -d, --daemonize
59              Daemonize after starting children.
60
61       -u ID, --chuid=ID
62              Change user ID in daemon mode (and group ID if  given,  separate
63              with colon.)
64
65       --pidfile=FILE
66              Write own process ID to FILE in daemon mode.
67
68       --stdout=FILE
69              Redirect stdout to FILE in daemon mode.
70
71       --stderr=FILE
72              Redirect stderr to FILE in daemon mode.
73
74       -w WATCH, --watch=WATCH
75              Watch  the  given file's modification time. If the file changes,
76              the web server will restart gracefully, allowing old requests to
77              complete  in the old processes while starting new processes with
78              the latest code or configuration.
79
80       -r RELOAD, --reload=RELOAD
81              If --reload=dev is passed, reload any time a  loaded  module  or
82              configuration file changes.
83
84       --deadman=DEADMAN_TIMEOUT, --deadman_timeout=DEADMAN_TIMEOUT
85              When  killing  an  old i/o process because the code has changed,
86              don't wait any longer than the deadman  timeout  value  for  the
87              process  to  gracefully exit. If all requests have not completed
88              by the deadman timeout, the process will be mercilessly killed.
89
90       -l ACCESS_LOG_FILE, --access-log-file=ACCESS_LOG_FILE
91              The file to log access log lines to. If not given, log  to  std‐
92              out. Pass /dev/null to discard logs.
93
94       -c, --coverage
95              If given, gather coverage data from the running program and make
96              the coverage report available from the /_coverage url.  See  the
97              figleaf           docs          for          more          info:
98              http://darcs.idyll.org/~t/projects/figleaf/doc/
99
100       --sysinfo
101              If given, gather system information data  and  make  the  report
102              available from the /_sysinfo url.
103
104       -m MAX_MEMORY, --max-memory=MAX_MEMORY
105              If given, the maximum amount of memory this instance of Spawning
106              is allowed to use. If all  of  the  processes  started  by  this
107              Spawning  controller use more than this amount of memory, send a
108              SIGHUP to the controller to get the children to restart.
109
110       --backdoor
111              Start a backdoor bound to localhost:3000
112
113       -a MAX_AGE, --max-age=MAX_AGE
114              If given, the maximum amount of time (in seconds) an instance of
115              spawning_child  is  allowed  to  run.  Once  this time limit has
116              expired the child willgracefully kill itself  while  the  server
117              starts a replacement.
118
119       --no-keepalive
120              Disable HTTP/1.1 KeepAlive
121
122       -z RESTART_ARGS, --z-restart-args=RESTART_ARGS
123              For internal use only
124
125       --status-port=STATUS_PORT
126              If  given,  hosts  a server status page at that port.  Two pages
127              are served: a human-readable HTML  version  at  http://host:sta‐
128              tus_port/status,    and    a    machine-readable    version   at
129              http://host:status_port/status.json
130
131       --status-host=STATUS_HOST
132              If given, binds the server status page to the specified local ip
133              address.   Defaults  to  the  same  value  as --host.  If --sta‐
134              tus-port is not supplied, the status page will not be activated.
135

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

SEE ALSO