UWSGI_ALARM_CURL(1)

๐Ÿ’– UWSGI_ALARM_CURL(1) ๐Ÿ’–

okay bestie, this is the User Commands manual page for uwsgi_alarm_curl, and it's lowkey iconic. no cap, we're about to go through all the flags. periodt. ๐Ÿ’…

โœจ NAME โœจ

uwsgi_alarm_curl โ€” it's giving fast (pure C), self-healing, developer-friendly WSGI server. literally the whole package. ๐Ÿซถ

๐ŸŒธ SYNOPSIS ๐ŸŒธ

uwsgi-core [options...]

๐Ÿ’… DESCRIPTION ๐Ÿ’…

okay so here's the vibe: you got a million options and every single one matters. let's get into it, bestie. don't skip a single one, because we keep all the details. โœจ

  • -s, --socket โ€” bind to the specified UNIX/TCP socket using default protocol ๐ŸŒˆ
  • -s, --uwsgi-socket โ€” bind to the specified UNIX/TCP socket using uwsgi protocol ๐Ÿ’–
  • --suwsgi-socket โ€” bind to the specified UNIX/TCP socket using uwsgi protocol over SSL ๐Ÿ”’
  • --ssl-socket โ€” bind to the specified UNIX/TCP socket using uwsgi protocol over SSL โœจ
  • --http-socket โ€” bind to the specified UNIX/TCP socket using HTTP protocol ๐ŸŒ
  • --http-socket-modifier1 โ€” force the specified modifier1 when using HTTP protocol ๐Ÿ’…
  • --http-socket-modifier2 โ€” force the specified modifier2 when using HTTP protocol ๐Ÿ’…
  • --http11-socket โ€” bind to the specified UNIX/TCP socket using HTTP 1.1 (Keep-Alive) protocol ๐Ÿ”
  • --https-socket โ€” bind to the specified UNIX/TCP socket using HTTPS protocol ๐Ÿ”
  • --https-socket-modifier1 โ€” force the specified modifier1 when using HTTPS protocol ๐Ÿ’…
  • --https-socket-modifier2 โ€” force the specified modifier2 when using HTTPS protocol ๐Ÿ’…
  • --fastcgi-socket โ€” bind to the specified UNIX/TCP socket using FastCGI protocol โšก
  • --fastcgi-nph-socket โ€” bind to the specified UNIX/TCP socket using FastCGI protocol (nph mode) โšก
  • --fastcgi-modifier1 โ€” force the specified modifier1 when using FastCGI protocol ๐Ÿ’…
  • --fastcgi-modifier2 โ€” force the specified modifier2 when using FastCGI protocol ๐Ÿ’…
  • --scgi-socket โ€” bind to the specified UNIX/TCP socket using SCGI protocol ๐ŸŒ€
  • --scgi-nph-socket โ€” bind to the specified UNIX/TCP socket using SCGI protocol (nph mode) ๐ŸŒ€
  • --scgi-modifier1 โ€” force the specified modifier1 when using SCGI protocol ๐Ÿ’…
  • --scgi-modifier2 โ€” force the specified modifier2 when using SCGI protocol ๐Ÿ’…
  • --raw-socket โ€” bind to the specified UNIX/TCP socket using RAW protocol ๐Ÿงช
  • --raw-modifier1 โ€” force the specified modifier1 when using RAW protocol ๐Ÿ’…
  • --raw-modifier2 โ€” force the specified modifier2 when using RAW protocol ๐Ÿ’…
  • --puwsgi-socket โ€” bind to the specified UNIX/TCP socket using persistent uwsgi protocol (puwsgi) ๐Ÿ”
  • --protocol โ€” force the specified protocol for default sockets ๐Ÿ’ซ
  • --socket-protocol โ€” force the specified protocol for default sockets ๐Ÿ’ซ
  • --shared-socket โ€” create a shared socket for advanced jailing or ipc ๐Ÿค
  • --undeferred-shared-socket โ€” create a shared socket for advanced jailing or ipc (undeferred mode) ๐Ÿค
  • -p, --processes โ€” spawn the specified number of workers/processes ๐Ÿ‘ฏ
  • -p, --workers โ€” spawn the specified number of workers/processes ๐Ÿ‘ฏ
  • --thunder-lock โ€” serialize accept() usage (if possible) โšก
  • -t, --harakiri โ€” set harakiri timeout ๐Ÿ—ก๏ธ
  • --harakiri-verbose โ€” enable verbose mode for harakiri ๐Ÿ“ข
  • --harakiri-graceful-timeout โ€” interval between graceful harakiri attempt and a sigkill โณ
  • --harakiri-graceful-signal โ€” use this signal instead of sigterm for graceful harakiri attempts ๐Ÿšฆ
  • --harakiri-queue-threshold โ€” only trigger harakiri if queue is greater than this threshold ๐Ÿ“Š
  • --harakiri-no-arh โ€” do not enable harakiri during after-request-hook ๐Ÿšซ
  • --no-harakiri-arh โ€” do not enable harakiri during after-request-hook ๐Ÿšซ
  • --no-harakiri-after-req-hook โ€” do not enable harakiri during after-request-hook ๐Ÿšซ
  • --backtrace-depth โ€” set backtrace depth ๐Ÿชœ
  • --mule-harakiri โ€” set harakiri timeout for mule tasks ๐Ÿด
  • -x, --xmlconfig โ€” load config from xml file ๐Ÿ“„
  • -x, --xml โ€” load config from xml file ๐Ÿ“„
  • --config โ€” load configuration using the pluggable system ๐Ÿ”Œ
  • --fallback-config โ€” re-exec uwsgi with the specified config when exit code is 1 ๐Ÿ”„
  • --strict โ€” enable strict mode (placeholder cannot be used) ๐Ÿšจ
  • --skip-zero โ€” skip check of file descriptor 0 0๏ธโƒฃ
  • --skip-atexit โ€” skip atexit hooks (ignored by the master) ๐Ÿšช
  • --skip-atexit-teardown โ€” skip atexit teardown (ignored by the master) ๐Ÿงน
  • -S, --set โ€” set a placeholder or an option ๐Ÿ“Œ
  • --set-placeholder โ€” set a placeholder ๐Ÿ“Œ
  • --set-ph โ€” set a placeholder ๐Ÿ“Œ
  • --get โ€” print the specified option value and exit ๐Ÿ–จ๏ธ
  • --declare-option โ€” declare a new uWSGI custom option ๐Ÿ†•
  • --declare-option2 โ€” declare a new uWSGI custom option (non-immediate) ๐Ÿ†•
  • --resolve โ€” place the result of a dns query in the specified placeholder, sytax: placeholder=name (immediate option) ๐Ÿ”
  • --for โ€” (opt logic) for cycle ๐Ÿ”
  • --for-glob โ€” (opt logic) for cycle (expand glob) ๐Ÿ”
  • --for-times โ€” (opt logic) for cycle (expand the specified num to a list starting from 1) ๐Ÿ”‚
  • --for-readline โ€” (opt logic) for cycle (expand the specified file to a list of lines) ๐Ÿ“„
  • --endfor โ€” (opt logic) end for cycle ๐Ÿ›‘
  • --end-for โ€” (opt logic) end for cycle ๐Ÿ›‘
  • --if-opt โ€” (opt logic) check for option โ“
  • --if-not-opt โ€” (opt logic) check for option โ“
  • --if-env โ€” (opt logic) check for environment variable ๐ŸŒฟ
  • --if-not-env โ€” (opt logic) check for environment variable ๐ŸŒฟ
  • --ifenv โ€” (opt logic) check for environment variable ๐ŸŒฟ
  • --if-reload โ€” (opt logic) check for reload ๐Ÿ”„
  • --if-not-reload โ€” (opt logic) check for reload ๐Ÿ”„
  • --if-hostname โ€” (opt logic) check for hostname ๐Ÿท๏ธ
  • --if-not-hostname โ€” (opt logic) check for hostname ๐Ÿท๏ธ
  • --if-hostname-match โ€” (opt logic) try to match hostname against a regular expression ๐Ÿ”Ž
  • --if-not-hostname-match โ€” (opt logic) try to match hostname against a regular expression ๐Ÿ”Ž
  • --if-exists โ€” (opt logic) check for file/directory existence ๐Ÿ“
  • --if-not-exists โ€” (opt logic) check for file/directory existence ๐Ÿ“
  • --ifexists โ€” (opt logic) check for file/directory existence ๐Ÿ“
  • --if-plugin โ€” (opt logic) check for plugin ๐Ÿ”Œ
  • --if-not-plugin โ€” (opt logic) check for plugin ๐Ÿ”Œ
  • --ifplugin โ€” (opt logic) check for plugin ๐Ÿ”Œ
  • --if-file โ€” (opt logic) check for file existence ๐Ÿ“„
  • --if-not-file โ€” (opt logic) check for file existence ๐Ÿ“„
  • --if-dir โ€” (opt logic) check for directory existence ๐Ÿ“‚
  • --if-not-dir โ€” (opt logic) check for directory existence ๐Ÿ“‚
  • --ifdir โ€” (opt logic) check for directory existence ๐Ÿ“‚
  • --if-directory โ€” (opt logic) check for directory existence ๐Ÿ“‚
  • --endif โ€” (opt logic) end if ๐Ÿ›‘
  • --end-if โ€” (opt logic) end if ๐Ÿ›‘
  • --blacklist โ€” set options blacklist context ๐Ÿšซ
  • --end-blacklist โ€” clear options blacklist context ๐Ÿšซ
  • --whitelist โ€” set options whitelist context โœ…
  • --end-whitelist โ€” clear options whitelist context โœ…
  • --ignore-sigpipe โ€” do not report (annoying) SIGPIPE ๐Ÿ”‡
  • --ignore-write-errors โ€” do not report (annoying) write()/writev() errors ๐Ÿ”‡
  • --write-errors-tolerance โ€” set the maximum number of allowed write errors (default: no tolerance) ๐Ÿ“‰
  • --write-errors-exception-only โ€” only raise an exception on write errors giving control to the app itself ๐ŸŽฎ
  • --disable-write-exception โ€” disable exception generation on write()/writev() ๐Ÿšซ
  • --inherit โ€” use the specified file as config template ๐Ÿ“‹
  • --include โ€” include the specified file as immediate configuration ๐Ÿ“Ž
  • --inject-before โ€” inject a text file before the config file (advanced templating) ๐Ÿ’‰
  • --inject-after โ€” inject a text file after the config file (advanced templating) ๐Ÿ’‰
  • -d, --daemonize โ€” daemonize uWSGI ๐Ÿ‘ป
  • --daemonize2 โ€” daemonize uWSGI after app loading ๐Ÿ‘ป
  • --stop โ€” stop an instance ๐Ÿ›‘
  • --reload โ€” reload an instance ๐Ÿ”„
  • --pause โ€” pause an instance โธ๏ธ
  • --suspend โ€” suspend an instance โธ๏ธ
  • --resume โ€” resume an instance โ–ถ๏ธ
  • --connect-and-read โ€” connect to a socket and wait for data from it ๐Ÿ”Œ
  • --extract โ€” fetch/dump any supported address to stdout ๐Ÿ“ค
  • -l, --listen โ€” set the socket listen queue size ๐Ÿ“
  • -v, --max-vars โ€” set the amount of internal iovec/vars structures ๐Ÿ“ฆ
  • --max-apps โ€” set the maximum number of per-worker applications ๐Ÿ“ฑ
  • -b, --buffer-size โ€” set internal buffer size ๐Ÿงบ
  • -m, --memory-report โ€” enable memory report ๐Ÿ“Š
  • --profiler โ€” enable the specified profiler ๐Ÿ“ˆ
  • -c, --cgi-mode โ€” force CGI-mode for plugins supporting it ๐Ÿข
  • -a, --abstract-socket โ€” force UNIX socket in abstract mode (Linux only) ๐Ÿง
  • -C, --chmod-socket โ€” chmod-socket ๐Ÿ”
  • -C, --chmod โ€” chmod-socket ๐Ÿ”
  • --chown-socket โ€” chown unix sockets ๐Ÿ‘‘
  • --umask โ€” set umask ๐ŸŽญ
  • --freebind โ€” put socket in freebind mode ๐Ÿ•Š๏ธ
  • --map-socket โ€” map sockets to specific workers ๐Ÿ—บ๏ธ
  • -T, --enable-threads โ€” enable threads (stub option this is true by default) ๐Ÿงต
  • --no-threads-wait โ€” do not wait for threads cancellation on quit/reload ๐Ÿšซ
  • --auto-procname โ€” automatically set processes name to something meaningful ๐Ÿท๏ธ
  • --procname-prefix โ€” add a prefix to the process names โž•
  • --procname-prefix-spaced โ€” add a spaced prefix to the process names โž•
  • --procname-append โ€” append a string to process names โž•
  • --procname โ€” set process names ๐Ÿ“›
  • --procname-master โ€” set master process name ๐Ÿ‘‘
  • -i, --single-interpreter โ€” do not use multiple interpreters (where available) 1๏ธโƒฃ
  • --need-app โ€” exit if no app can be loaded ๐Ÿšช
  • -M, --master โ€” enable master process ๐Ÿ‘‘
  • --honour-stdin โ€” do not remap stdin to /dev/null โŒจ๏ธ
  • --emperor โ€” run the Emperor ๐Ÿ‘‘
  • --emperor-proxy-socket โ€” force the vassal to became an Emperor proxy ๐Ÿ‘‘
  • --emperor-wrapper โ€” set a binary wrapper for vassals ๐Ÿงฐ
  • --emperor-wrapper-override โ€” set a binary wrapper for vassals to try before the default one ๐Ÿงฐ
  • --emperor-wrapper-fallback โ€” set a binary wrapper for vassals to try as a last resort ๐Ÿงฐ
  • --emperor-nofollow โ€” do not follow symlinks when checking for mtime ๐Ÿ”—
  • --emperor-procname โ€” set the Emperor process name ๐Ÿ‘‘
  • --emperor-freq โ€” set the Emperor scan frequency (default 3 seconds) โฒ๏ธ
  • --emperor-required-heartbeat โ€” set the Emperor tolerance about heartbeats ๐Ÿ’“
  • --emperor-curse-tolerance โ€” set the Emperor tolerance about cursed vassals ๐Ÿง™
  • --emperor-pidfile โ€” writes the Emperor's pid into the file you point at. King needs a name tag bestie ๐Ÿ’–
  • --emperor-tyrant โ€” flips the Emperor into Tyrant mode. Yeah the name is dramatic, that's the whole point.
  • --emperor-tyrant-nofollow โ€” in Tyrant mode, do NOT follow symlinks while it's checking uid/gid. No shortcuts, no sneaky links ๐Ÿšซ
  • --emperor-stats โ€” runs the Emperor stats server โœจ
  • --emperor-stats-server โ€” runs the Emperor stats server (same vibe, different spelling, both real)
  • --early-emperor โ€” spawn the emperor ASAP, no waiting around ๐Ÿ’…
  • --emperor-broodlord โ€” runs the emperor in BroodLord mode ๐Ÿ‘‘
  • --emperor-throttle โ€” sets the throttling level, in milliseconds, for vassals that are acting up (default 1000)
  • --emperor-max-throttle โ€” sets the MAX throttling level, in milliseconds, for vassals that are acting all the way up (default 3 minutes)
  • --emperor-magic-exec โ€” prefixes vassals' config files with exec:// if they have the executable bit set ๐Ÿช„
  • --emperor-on-demand-extension โ€” searches for a text file named vassal name + extension that holds the on demand socket name
  • --emperor-on-demand-ext โ€” searches for a text file named vassal name + extension that holds the on demand socket name (the short king version)
  • --emperor-on-demand-directory โ€” turns on on demand mode, binding to the unix socket inside the directory you specify, named like the vassal + .socket
  • --emperor-on-demand-dir โ€” same thing, shorter flag, same energy: on demand mode, unix socket in your directory, named like the vassal + .socket
  • --emperor-on-demand-exec โ€” uses the output of the command you specify as the on demand socket name (your vassal's name gets passed in as the only argument)
  • --emperor-extra-extension โ€” lets the Emperor accept the extension you specify (the vassal gets called with --config)
  • --emperor-extra-ext โ€” lets the Emperor accept the extension you specify (and yep, the vassal gets called with --config)
  • --emperor-no-blacklist โ€” disables the Emperor blacklisting subsystem entirely ๐Ÿšซ
  • --emperor-use-clone โ€” uses clone() instead of fork(), passing along the unshare() flags you specify
  • --emperor-graceful-shutdown โ€” vassals get a graceful shutdown during ragnarok ๐Ÿ•Š๏ธ (yes it really says ragnarok)
  • --emperor-cap โ€” sets the vassals capability
  • --vassals-cap โ€” sets the vassals capability
  • --vassal-cap โ€” sets the vassals capability (three flags, one job, pick your fave)
  • --imperial-monitor-list โ€” lists the enabled imperial monitors ๐Ÿ‘€
  • --imperial-monitors-list โ€” lists the enabled imperial monitors (plural spelling gang)
  • --vassals-inherit โ€” adds config templates to vassals config (it uses --inherit)
  • --vassals-include โ€” includes config templates into vassals config (it uses --include instead of --inherit)
  • --vassals-inherit-before โ€” adds config templates to vassals config (uses --inherit, and parses before the vassal file)
  • --vassals-include-before โ€” includes config templates into vassals config (uses --include instead of --inherit, and parses before the vassal file)
  • --vassals-start-hook โ€” runs the command you specify before each vassal starts ๐Ÿ
  • --vassals-stop-hook โ€” runs the command you specify after a vassal's death ๐Ÿชฆ
  • --vassal-sos โ€” asks the emperor for backup when the vassal is overloaded. literally screaming SOS ๐Ÿ˜ญ
  • --vassal-sos-backlog โ€” asks the emperor for sos if the backlog queue has more items than the value you specify
  • --vassals-set โ€” automatically sets the option you specify (via --set) for every vassal
  • --vassal-set โ€” automatically sets the option you specify (via --set) for every vassal (singular flag, same deal)
  • --heartbeat โ€” announces healthiness to the emperor ๐Ÿ’“
  • --reload-mercy โ€” sets the maximum time, in seconds, we wait for workers and other processes to die during reload/shutdown
  • --worker-reload-mercy โ€” sets the maximum time, in seconds, a worker can take to reload/shutdown (default is 60)
  • --mule-reload-mercy โ€” sets the maximum time, in seconds, a mule can take to reload/shutdown (default is 60)
  • --exit-on-reload โ€” forces exit even if a reload was requested
  • --die-on-term โ€” exits instead of doing a brutal reload on SIGTERM
  • --force-gateway โ€” forces the spawn of the first registered gateway, no master needed
  • -h|--help โ€” shows this help ๐Ÿซถ
  • -h|--usage โ€” shows this help (yep, both spellings, same answer)
  • --print-sym โ€” prints the content of the binary symbol you specify
  • --print-symbol โ€” prints the content of the binary symbol you specify (the long way to say it)
  • -r|--reaper โ€” calls waitpid(-1,...) after every request to get rid of zombies ๐ŸงŸ slay
  • -R|--max-requests โ€” reloads workers after the specified amount of managed requests
  • --max-requests-delta โ€” adds (worker_id * delta) to the max_requests value of each worker
  • --min-worker-lifetime โ€” the number of seconds a worker must run before it can be reloaded (default is 10)
  • --max-worker-lifetime โ€” reload workers after the specified amount of seconds (default is disabled)
  • --max-worker-lifetime-delta โ€” adds (worker_id * delta) seconds to the max_worker_lifetime value of each worker
  • -z|--socket-timeout โ€” sets the internal sockets timeout
  • --no-fd-passing โ€” disables file descriptor passing
  • --locks โ€” creates the number of shared locks you specify
  • --lock-engine โ€” sets the lock engine ๐Ÿ”’
  • --ftok โ€” sets the ipcsem key via ftok() so you avoid duplicates
  • --persistent-ipcsem โ€” does not remove ipcsem's on shutdown
  • -A|--sharedarea โ€” creates a raw shared memory area of the specified pages (heads up: it supports keyval too)
  • --safe-fd โ€” do not close the file descriptor you specify
  • --fd-safe โ€” do not close the file descriptor you specify (same protection, swapped order)
  • --cache โ€” creates a shared cache holding the given elements
  • --cache-blocksize โ€” sets the cache blocksize
  • --cache-store โ€” enables persistent cache to disk
  • --cache-store-sync โ€” sets the frequency of sync for the persistent cache
  • --cache-no-expire โ€” disables the auto sweep of expired items
  • --cache-expire-freq โ€” sets the frequency of cache sweeper scans (default 3 seconds)
  • --cache-report-freed-items โ€” constantly reports the cache item freed by the sweeper (use this only for debug, bestie, it's chatty ๐Ÿ—ฃ๏ธ)
  • --cache-udp-server โ€” binds the cache udp server to the socket you specify (only used for set/update/delete)
  • --cache-udp-node โ€” sends cache update/deletion to the cache udp server you specify
  • --cache-sync โ€” copies the whole content of another uWSGI cache server on server startup
  • --cache-use-last-modified โ€” updates the last_modified_at timestamp on every cache item modification (default is disabled)
  • --add-cache-item โ€” adds an item in the cache
  • --load-file-in-cache โ€” loads a static file in the cache
  • --load-file-in-cache-gzip โ€” loads a static file in the cache with gzip compression ๐Ÿ—œ๏ธ
  • --cache2 โ€” creates a new generation shared cache (keyval syntax)
  • --queue โ€” enables the shared queue
  • --queue-blocksize โ€” sets the queue blocksize
  • --queue-store โ€” enables persistent queue to disk
  • --queue-store-sync โ€” sets the frequency of sync for the persistent queue
  • -Q|--spooler โ€” runs a spooler on the directory you specify
  • --spooler-external โ€” maps spoolers requests to a spooler directory managed by an external instance
  • --spooler-ordered โ€” tries to order the execution of spooler tasks
  • --spooler-chdir โ€” chdir()s to the directory you specify before each spooler task
  • --spooler-processes โ€” sets the number of processes for spoolers
  • --spooler-quiet โ€” do not be verbose with spooler tasks ๐Ÿคซ
  • --spooler-max-tasks โ€” sets the maximum number of tasks to run before recycling a spooler
  • --spooler-harakiri โ€” sets the harakiri timeout for spooler tasks
  • --spooler-frequency โ€” sets the spooler frequency
  • --spooler-freq โ€” sets the spooler frequency (shortened, same dial)
  • --mule โ€” adds a mule ๐Ÿด
  • --mules โ€” adds the number of mules you specify
  • --farm โ€” adds a mule farm ๐Ÿด๐Ÿด๐Ÿด
  • --mule-msg-size โ€” sets the mule message buffer size
  • --signal โ€” sends a uwsgi signal to a server ๐Ÿ“ก
  • --signal-bufsize โ€” sets the buffer size for the signal queue
  • --signals-bufsize โ€” sets the buffer size for the signal queue (plural variant, identical job)
  • --signal-timer โ€” adds a timer (syntax: <signal> <seconds>) โฐ
  • --timer โ€” adds a timer (syntax: <signal> <seconds>)
  • --signal-rbtimer โ€” adds a redblack timer (syntax: <signal> <seconds>)
  • --rbtimer โ€” adds a redblack timer (syntax: <signal> <seconds>)
  • --rpc-max โ€” maximum number of rpc slots (default: 64)
  • -L|--disable-logging โ€” disables request logging
  • --flock โ€” locks the file you specify before starting, and exits if it's already locked
  • --flock-wait โ€” locks the file you specify before starting, and waits if it's already locked
  • --flock2 โ€” locks the file you specify after logging/daemon setup, and exits if it's locked
  • --flock-wait2 โ€” locks the file you specify after logging/daemon setup, and waits if it's locked
  • --pidfile โ€” creates a pidfile (this happens before privileges drop)
  • --pidfile2 โ€” creates a pidfile (this happens after privileges drop)
  • --safe-pidfile โ€” creates a safe pidfile (before privileges drop)
  • --safe-pidfile2 โ€” creates a safe pidfile (after privileges drop)
  • --chroot โ€” chroot()s to the directory you specify
  • --pivot-root โ€” pivot_root()s to the directories you specify (new_root and put_old must be separated with a space)
  • --pivot_root โ€” pivot_root()s to the directories you specify (new_root and put_old must be separated with a space โ€” yep, underscore version, same rule)
  • --uid โ€” setuid to the user/uid you specify
  • --gid โ€” setgid to the group/gid you specify
  • --add-gid โ€” adds the group id you specify to the process credentials
  • --immediate-uid โ€” setuid to the user/uid you specify, IMMEDIATELY
  • --immediate-gid โ€” setgid to the group/gid you specify, IMMEDIATELY
  • --no-initgroups โ€” disables the additional groups that get set via initgroups()
  • --cap โ€” sets the process capability
  • --unshare โ€” unshare()s part of the processes and drops them into a new namespace
  • --unshare2 โ€” unshare()s part of the processes and drops them into a new namespace after the rootfs change
  • --setns-socket โ€” exposes a unix socket returning namespace fds from /proc/self/ns
  • --setns-socket-skip โ€” skips the entry you specify when sending setns file descriptors
  • --setns-skip โ€” skips the entry you specify when sending setns file descriptors (short version, same skip)
  • --setns โ€” joins a namespace created by an external uWSGI instance
  • --setns-preopen โ€” opens /proc/self/ns as soon as possible and caches the fds
  • --jailed โ€” stamps this instance as jailed ๐Ÿ’… and forces the post_jail hooks to actually fire. no jail left behind, periodt.
  • --refork โ€” does a fork() again after privileges drop. lowkey iconic for jailing systems.
  • --re-fork โ€” same thing, different spelling โœจ fork() again after privileges drop, and yes it's for jailing systems.
  • --refork-as-root โ€” fork() again before privileges drop. also for jailing systems, bestie ๐ŸŒธ
  • --re-fork-as-root โ€” the hyphenated twin ๐Ÿซถ fork() again before privileges drop, built for jailing systems.
  • --refork-post-jail โ€” fork() again after jailing. jailing systems, you know the vibe ๐Ÿ‘‘
  • --re-fork-post-jail โ€” same energy, extra hyphen ๐ŸŽ€ fork() again after jailing, for jailing systems.

okay so now we're in HOOK CITY and honestly? it's giving main character โœจ every one of these runs the specified hook at a different โœจmomentโœจ in the lifecycle.

๐Ÿฆ‹ the hook timing lore

  • --hook-asap โ€” run the specified hook as soon as possible. literally the second it can ๐Ÿƒโ€โ™€๏ธ
  • --hook-pre-jail โ€” run the specified hook before jailing.
  • --hook-post-jail โ€” run the specified hook after jailing.
  • --hook-in-jail โ€” run the specified hook in jail after initialization.
  • --hook-as-root โ€” run the specified hook before privileges drop ๐Ÿ‘‘
  • --hook-as-user โ€” run the specified hook after privileges drop.
  • --hook-as-user-atexit โ€” run the specified hook before app exit and reload.
  • --hook-pre-app โ€” run the specified hook before app loading.
  • --hook-post-app โ€” run the specified hook after app loading.
  • --hook-post-fork โ€” run the specified hook after each fork ๐Ÿด
  • --hook-accepting โ€” run the specified hook after each worker enter the accepting phase.
  • --hook-accepting1 โ€” run the specified hook after the first worker enters the accepting phase ๐Ÿฅ‡
  • --hook-accepting-once โ€” run the specified hook after each worker enter the accepting phase, but once per-instance (not once per worker, bestie).
  • --hook-accepting1-once โ€” run the specified hook after the first worker enters the accepting phase, once per instance.
  • --hook-master-start โ€” run the specified hook when the Master starts ๐Ÿ‘‘
  • --hook-touch โ€” run the specified hook when the specified file is touched. syntax goes like this: (syntax: <file> <action>) ๐Ÿ‘€
  • --hook-emperor-start โ€” run the specified hook when the Emperor starts.
  • --hook-emperor-stop โ€” run the specified hook when the Emperor send a stop message.
  • --hook-emperor-reload โ€” run the specified hook when the Emperor send a reload message.
  • --hook-emperor-lost โ€” run the specified hook when the Emperor connection is lost ๐Ÿ˜ญ
  • --hook-as-vassal โ€” run the specified hook before exec()ing the vassal.
  • --hook-as-emperor โ€” run the specified hook in the emperor after the vassal has been started.
  • --hook-as-mule โ€” run the specified hook in each mule ๐Ÿด
  • --hook-as-gateway โ€” run the specified hook in each gateway ๐Ÿšช
  • --after-request-hook โ€” run the specified function/symbol after each request.
  • --after-request-call โ€” run the specified function/symbol after each request. (yes bestie, same description, it's a real option, not a typo ๐Ÿ’€)

๐Ÿ”ฅ exec squad, assemble

these run the specified command at every stage of the lifecycle:

  • --exec-asap โ€” run the specified command as soon as possible.
  • --exec-pre-jail โ€” run the specified command before jailing.
  • --exec-post-jail โ€” run the specified command after jailing.
  • --exec-in-jail โ€” run the specified command in jail after initialization.
  • --exec-as-root โ€” run the specified command before privileges drop ๐Ÿ‘‘
  • --exec-as-user โ€” run the specified command after privileges drop.
  • --exec-as-user-atexit โ€” run the specified command before app exit and reload.
  • --exec-pre-app โ€” run the specified command before app loading.
  • --exec-post-app โ€” run the specified command after app loading.
  • --exec-as-vassal โ€” run the specified command before exec()ing the vassal.
  • --exec-as-emperor โ€” run the specified command in the emperor after the vassal has been started.

๐Ÿงš mount / umount (filesystem fairy business)

  • --mount-asap โ€” mount filesystem as soon as possible.
  • --mount-pre-jail โ€” mount filesystem before jailing.
  • --mount-post-jail โ€” mount filesystem after jailing.
  • --mount-in-jail โ€” mount filesystem in jail after initialization.
  • --mount-as-root โ€” mount filesystem before privileges drop.
  • --mount-as-vassal โ€” mount filesystem before exec()ing the vassal.
  • --mount-as-emperor โ€” mount filesystem in the emperor after the vassal has been started.
  • --umount-asap โ€” unmount filesystem as soon as possible.
  • --umount-pre-jail โ€” unmount filesystem before jailing.
  • --umount-post-jail โ€” unmount filesystem after jailing.
  • --umount-in-jail โ€” unmount filesystem in jail after initialization.
  • --umount-as-root โ€” unmount filesystem before privileges drop.
  • --umount-as-vassal โ€” unmount filesystem before exec()ing the vassal.
  • --umount-as-emperor โ€” unmount filesystem in the emperor after the vassal has been started.

๐ŸŒธ waiting era (patience is a vibe)

  • --wait-for-interface โ€” wait for the specified network interface to come up before running root hooks.
  • --wait-for-interface-timeout โ€” set the timeout for wait-for-interface.
  • --wait-interface โ€” wait for the specified network interface to come up before running root hooks.
  • --wait-interface-timeout โ€” set the timeout for wait-for-interface.
  • --wait-for-iface โ€” wait for the specified network interface to come up before running root hooks.
  • --wait-for-iface-timeout โ€” set the timeout for wait-for-interface.
  • --wait-iface โ€” wait for the specified network interface to come up before running root hooks.
  • --wait-iface-timeout โ€” set the timeout for wait-for-interface.
bestie there are literally four spellings of the interface wait and four timeouts. they all do the same thing. i don't make the rules ๐Ÿ’…
  • --wait-for-fs โ€” wait for the specified filesystem item to appear before running root hooks.
  • --wait-for-file โ€” wait for the specified file to appear before running root hooks.
  • --wait-for-dir โ€” wait for the specified directory to appear before running root hooks.
  • --wait-for-mountpoint โ€” wait for the specified mountpoint to appear before running root hooks.
  • --wait-for-fs-timeout โ€” set the timeout for wait-for-fs/file/dir.
  • --wait-for-socket โ€” wait for the specified socket to be ready before loading apps.
  • --wait-for-socket-timeout โ€” set the timeout for wait-for-socket.

โญ call squad (functions only, no shell)

these call the specified function at the vibe-appropriate moment:

  • --call-asap โ€” call the specified function as soon as possible.
  • --call-pre-jail โ€” call the specified function before jailing.
  • --call-post-jail โ€” call the specified function after jailing.
  • --call-in-jail โ€” call the specified function in jail after initialization.
  • --call-as-root โ€” call the specified function before privileges drop ๐Ÿ‘‘
  • --call-as-user โ€” call the specified function after privileges drop.
  • --call-as-user-atexit โ€” call the specified function before app exit and reload.
  • --call-pre-app โ€” call the specified function before app loading.
  • --call-post-app โ€” call the specified function after app loading.
  • --call-as-vassal โ€” call the specified function() before exec()ing the vassal.
  • --call-as-vassal1 โ€” call the specified function(char *) before exec()ing the vassal.
  • --call-as-vassal3 โ€” call the specified function(char *, uid_t, gid_t) before exec()ing the vassal.
  • --call-as-emperor โ€” call the specified function() in the emperor after the vassal has been started.
  • --call-as-emperor1 โ€” call the specified function(char *) in the emperor after the vassal has been started.
  • --call-as-emperor2 โ€” call the specified function(char *, pid_t) in the emperor after the vassal has been started.
  • --call-as-emperor4 โ€” call the specified function(char *, pid_t, uid_t, gid_t) in the emperor after the vassal has been started.
see the numbers on the end? they're the arg count bestie, 1 = 1 arg, 2 = 2 args, 3 = 3 args, 4 = 4 args, no number = no args. slay ๐Ÿซถ

๐ŸŽ€ config files & instance identity

  • --ini โ€” load config from ini file.
  • -y|--yaml โ€” load config from yaml file.
  • -y|--yml โ€” load config from yaml file.
  • -j|--json โ€” load config from json file.
  • -j|--js โ€” load config from json file.
  • --weight โ€” weight of the instance (used by clustering/lb/subscriptions).
  • --auto-weight โ€” set weight of the instance (used by clustering/lb/subscriptions) automatically.
  • --no-server โ€” force no-server mode.
  • --command-mode โ€” force command mode.

๐Ÿ’œ socket & network tuning

  • --no-defer-accept โ€” disable deferred-accept on sockets.
  • --tcp-nodelay โ€” enable TCP NODELAY on each request.
  • --so-keepalive โ€” enable TCP KEEPALIVEs.
  • --so-send-timeout โ€” set SO_SNDTIMEO.
  • --socket-send-timeout โ€” set SO_SNDTIMEO.
  • --so-write-timeout โ€” set SO_SNDTIMEO.
  • --socket-write-timeout โ€” set SO_SNDTIMEO.
  • --socket-sndbuf โ€” set SO_SNDBUF.
  • --socket-rcvbuf โ€” set SO_RCVBUF.
  • --shutdown-sockets โ€” force calling shutdown() in addition to close() when sockets are destroyed.

๐ŸŒˆ memory & reload drama

  • --limit-as โ€” limit processes address space/vsz.
  • --limit-nproc โ€” limit the number of spawnable processes.
  • --reload-on-as โ€” reload if address space is higher than specified megabytes.
  • --reload-on-rss โ€” reload if rss memory is higher than specified megabytes.
  • --evil-reload-on-as โ€” force the master to reload a worker if its address space is higher than specified megabytes ๐Ÿ˜ˆ
  • --evil-reload-on-rss โ€” force the master to reload a worker if its rss memory is higher than specified megabytes ๐Ÿ˜ˆ
  • --mem-collector-freq โ€” set the memory collector frequency when evil reloads are in place.
  • --reload-on-fd โ€” reload if the specified file descriptor is ready.
  • --brutal-reload-on-fd โ€” brutal reload if the specified file descriptor is ready ๐Ÿ’€
  • --ksm โ€” enable Linux KSM.
  • --pcre-jit โ€” enable pcre jit (if available).
  • --never-swap โ€” lock all memory pages avoiding swapping.

๐Ÿ“ touch me โ†’ reload me

  • --touch-reload โ€” reload uWSGI if the specified file is modified/touched.
  • --touch-workers-reload โ€” trigger reload of (only) workers if the specified file is modified/touched.
  • --touch-mules-reload โ€” reload mules if the specified file is modified/touched.
  • --touch-spoolers-reload โ€” reload spoolers if the specified file is modified/touched.
  • --touch-chain-reload โ€” trigger chain reload if the specified file is modified/touched.
  • --touch-logrotate โ€” trigger logrotation if the specified file is modified/touched.
  • --touch-logreopen โ€” trigger log reopen if the specified file is modified/touched.
  • --touch-exec โ€” run command when the specified file is modified/touched. syntax: file command
  • --touch-signal โ€” it's giving watchdog energy.</p> When the file you named gets modified/touched, it raises a signal. Syntax is file signal, so you hand it both bestie: the path and the signal. ๐ŸŽ€
  • --fs-reload โ€” if the filesystem object you specified gets modified, do a graceful reload. Softly softly, no drama. ๐Ÿฆ‹
  • --fs-brutal-reload โ€” same vibe check, different ending: the filesystem object gets modified, so we do a brutal reload. No chill. Periodt. ๐Ÿ’€
  • --fs-signal โ€” filesystem object changes โ†’ raise a uwsgi signal. Syntax: file signal. โœจ
  • --check-mountpoint โ€” if a filesystem is no longer reachable, destroy the instance. Sounds harsh but it's genuinely useful for reliable Fuse management, iykyk. ๐Ÿ’…
  • --mountpoint-check โ€” literally the same thing as --check-mountpoint: filesystem unreachable โ†’ instance destroyed. Useful for reliable Fuse management. ๐ŸŒธ
  • --check-mount โ€” okay so this is again the exact same deal. No filesystem, no instance. Useful for reliable Fuse management. ๐Ÿซถ
  • --mount-check โ€” bestie this one is also the same: if the filesystem becomes unreachable, the instance gets destroyed. Useful for reliable Fuse management. Four options, one vibe. ๐Ÿ‘‘
  • --propagate-touch โ€” the manpage calls this "over-engineering option for system with flaky signal management." So likeโ€ฆ a whole elaborate fit for a signal system that can't communicate. We love an overbuilt queen. ๐Ÿ’œ
  • --limit-post โ€” put a cap on the request body. ๐Ÿ“
  • --no-orphans โ€” if the master dies, the workers get automatically killed. Keeping the family together, kind of. โš ๏ธ Heads up though: it can be dangerous for availability.
  • --prio โ€” set the priority for your processes/threads. โœจ
  • --cpu-affinity โ€” set the cpu affinity. Pinning your faves to their seats. ๐ŸŽ€
  • --post-buffering โ€” sets the size in bytes at which post buffering switches from memory to buffering to disk instead. So: past this many bytes, it's disk time. ๐Ÿ’พ
  • --post-buffering-bufsize โ€” sets the buffer size used for read() while you're in post buffering mode. ๐ŸŒˆ
  • --body-read-warning โ€” sets how much memory allocation (in megabytes) is allowed for a request body before it starts printing a warning at you. It's giving concerned bestie. ๐Ÿ˜ญ
  • --upload-progress โ€” turn on creation of .json files inside the directory you specify, while a file upload is happening. Watch it in real time. โœจ
  • --no-default-app โ€” do not fallback to the default app. Boundaries! ๐Ÿšซ
  • --manage-script-name โ€” automatically rewrite SCRIPT_NAME and PATH_INFO for you. Queen behavior. ๐Ÿ‘‘
  • --ignore-script-name โ€” just ignore SCRIPT_NAME entirely. Not your problem, not your business. ๐Ÿ™ˆ
  • --catch-exceptions โ€” report the exception as http output. The manpage is very clear here: discouraged, use it only for testing. Testing-only, bestie, do not ship it. โš ๏ธ
  • --reload-on-exception โ€” when an exception is raised, reload that worker. Fresh start energy. ๐Ÿ”„
  • --reload-on-exception-type โ€” reload the worker when a specific exception type is raised. Picky and valid. ๐Ÿ’…
  • --reload-on-exception-value โ€” reload the worker when a specific exception value is raised. ๐ŸŽฏ
  • --reload-on-exception-repr โ€” reload the worker when a specific exception type+value (language-specific, so this is speaking your app's language) is raised. ๐ŸŒธ
  • --exception-handler โ€” add an exception handler. ๐Ÿซถ
  • --enable-metrics โ€” turn the metrics subsystem on. Numbers era begins. ๐Ÿ”ฅ
  • --metric โ€” add a custom metric. Make it yours. โญ
  • --metric-threshold โ€” add a metric threshold/alarm. When the number crosses the line, alarm goes off. ๐Ÿšจ
  • --metric-alarm โ€” also adds a metric threshold/alarm. Same beautiful thing, different name. ๐Ÿ’–
  • --alarm-metric โ€” yep, another metric threshold/alarm. They really said "three names, one feature." ๐Ÿ˜ญ
  • --metrics-dir โ€” export your metrics as text files into the directory you name. ๐Ÿ—‚๏ธ
  • --metrics-dir-restore โ€” restore the last value that was taken from the metrics dir. Picking up right where you left off. ๐Ÿ’ซ
  • --metric-dir โ€” export metrics as text files to the specified directory. (Yes, singular "metric". Yes, same thing. No, I don't make the rules.) ๐ŸŽ€
  • --metric-dir-restore โ€” restore the last value taken from the metrics dir. Again, the singular twin. ๐Ÿฆ‹
  • --metrics-no-cores โ€” disable generation of cores-related metrics. Bye to the cores numbers. ๐Ÿ™ˆ

  • --udp โ€” run the udp server on the address you specify. ๐Ÿ“ก
  • --stats โ€” enable the stats server on the specified address. ๐ŸŒŸ
  • --stats-server โ€” also enables the stats server on the specified address. Same icon, same vibe. โœจ
  • --stats-http โ€” prefix the stats server json output with http headers. Fancy little hat on your json. ๐ŸŽ€
  • --stats-minified โ€” minify the statistics json output. Compact queen. ๐Ÿ’…
  • --stats-min โ€” minify the statistics json output. The short nickname for the same thing. โญ
  • --stats-push โ€” push the stats json to the destination you specify. Sending it straight to its location. ๐Ÿ“ค
  • --stats-pusher-default-freq โ€” set the default frequency of stats pushers. How often the pushing happens. โฐ
  • --stats-pushers-default-freq โ€” set the default frequency of stats pushers. Plural spelling, same heartbeat. ๐Ÿซถ
  • --stats-no-cores โ€” disable generation of cores-related stats. ๐Ÿšซ
  • --stats-no-metrics โ€” do not include metrics in the stats output. Metrics stay out of this one. ๐ŸŒธ
  • --multicast โ€” subscribe to the multicast group you specify. ๐Ÿ“ป
  • --multicast-ttl โ€” set the multicast ttl. ๐Ÿ•ฐ๏ธ
  • --multicast-loop โ€” set the multicast loop. Default is 1. ๐ŸŒˆ
  • --master-fifo โ€” enable the master fifo. One little pipe, so much power. ๐ŸŽ€
  • --notify-socket โ€” enable the notification socket. ๐Ÿ””
  • --subscription-notify-socket โ€” set the notification socket specifically for subscriptions. Same socket energy, subscriptions-only. โœ‰๏ธ
  • --legion โ€” become a member of a legion. Yes, a legion. It's giving chosen family. โš”๏ธ
  • --legion-mcast โ€” become a member of a legion, but as a shortcut for multicast. Speedrun version. ๐Ÿƒโ€โ™€๏ธ
  • --legion-node โ€” add a node to a legion. New member, welcome to the group chat. ๐Ÿ’Œ
  • --legion-freq โ€” set the frequency of legion packets. ๐Ÿ’“
  • --legion-tolerance โ€” set the tolerance of the legion subsystem. Grace has limits, bestie. โš–๏ธ
  • --legion-death-on-lord-error โ€” if one of the lord hooks fails, it declares itself a dead node for however many seconds you specify. Dramatic but documented. ๐Ÿ’€
  • --legion-skew-tolerance โ€” set the clock skew tolerance of the legion subsystem. Default is 60 seconds. โฑ๏ธ
  • --legion-lord โ€” the action to call on Lord election. ๐Ÿ‘‘
  • --legion-unlord โ€” the action to call on Lord dismiss. The crown comes off. ๐Ÿ‘‹
  • --legion-setup โ€” the action to call on legion setup. ๐Ÿ› ๏ธ
  • --legion-death โ€” the action to call on legion death, which means shutdown of the instance. ๐Ÿ˜ญ
  • --legion-join โ€” the action to call on legion join, which fires the first time quorum is reached. ๐ŸŽ‰
  • --legion-node-joined โ€” the action to call when a new node joins the legion. ๐Ÿซถ
  • --legion-node-left โ€” the action to call when a node leaves the legion. ๐Ÿฅฒ
  • --legion-quorum โ€” set the quorum of a legion. ๐Ÿ—ณ๏ธ
  • --legion-scroll โ€” set the scroll of a legion. ๐Ÿ“œ
  • --legion-scroll-max-size โ€” set the max size of the legion scroll buffer. ๐Ÿ—’๏ธ
  • --legion-scroll-list-max-size โ€” set the max size of the legion scroll list buffer. Yes, that's a different buffer from the one above. ๐Ÿ’…
  • --subscriptions-sign-check โ€” set the digest algorithm and the certificate directory for the secured subscription system. ๐Ÿ”
  • --subscriptions-sign-check-tolerance โ€” set the maximum tolerance (in seconds) of clock skew for the secured subscription system. โณ
  • --subscriptions-sign-skip-uid โ€” when using unix sockets credentials, skip the signature check for the uid you specify. VIP pass. ๐ŸŽŸ๏ธ
  • --subscriptions-credentials-check โ€” add a directory to search for subscriptions key credentials. ๐Ÿ—‚๏ธ
  • --subscriptions-use-credentials โ€” enable management of SCM_CREDENTIALS in subscriptions UNIX sockets. ๐Ÿ”‘
  • --subscription-algo โ€” set the load balancing algorithm for the subscription system. Pick your fighter. โš”๏ธ
  • --subscription-dotsplit โ€” try to fallback to the next part (dot based) in the subscription key. Following the dots. ๐Ÿ”ต
  • --subscribe-to โ€” subscribe to the subscription server you specify. ๐Ÿค
  • --st โ€” subscribe to the specified subscription server. Tiny name, big job. โœจ
  • --subscribe โ€” subscribe to the specified subscription server. The classic. ๐Ÿ’–
  • --subscribe2 โ€” subscribe to the specified subscription server using advanced keyval syntax. The sequel, and it's more sophisticated. ๐Ÿ’…
  • --subscribe-freq โ€” send the subscription announce at the interval you specify. โฐ
  • --subscription-tolerance โ€” set the tolerance for subscription servers. ๐Ÿซถ
  • --unsubscribe-on-graceful-reload โ€” force the unsubscribe request even during a graceful reload. No lingering subscriptions, we're leaving cleanly. ๐Ÿšช
  • --start-unsubscribed โ€” configure your subscriptions but don't actually send them. The manpage notes this is useful with master fifo. All dressed up, not going anywhere (yet). ๐Ÿ‘—
  • --subscribe-with-modifier1 โ€” force the specified modifier1 when subscribing. ๐ŸŽš๏ธ
  • --snmp โ€” enable the embedded snmp server. ๐ŸŒ
  • --snmp-community โ€” set the snmp community string. ๐ŸŽ€

  • --ssl-verbose โ€” be verbose about SSL errors. Spill the tea on every handshake problem. โ˜•
  • --ssl-verify-depth โ€” set the maximum certificate verification depth. How far down the chain we're willing to look. ๐Ÿ”
  • --sni โ€” add an SNI-governed SSL context. ๐ŸŒธ
  • --sni-dir โ€” check for the cert/key/client_ca file in the directory you specify, and create a sni/ssl context on demand. Lazy loading but make it SSL. โœจ
  • --sni-dir-ciphers โ€” set the ssl ciphers for the sni-dir option. ๐Ÿงš
  • --ssl-enable3 โ€” enable SSLv3. The manpage says it plainly: insecure. โš ๏ธ Like, we're telling you for your own good.
  • --ssl-enable-sslv3 โ€” enable SSLv3. Also insecure. Same warning, longer name. ๐Ÿ’€
  • --ssl-enable-tlsv1 โ€” enable TLSv1. Also insecure, bestie. Do not. ๐Ÿšฉ
  • --ssl-option โ€” set a raw ssl option, and it takes a numeric value. Raw and numeric, exactly as stated. ๐Ÿ”ข
  • --sni-regexp โ€” add an SNI-governed SSL context where the key is a regexp. Pattern-matching your way into SSL. ๐Ÿงฉ
  • --ssl-tmp-dir โ€” store ssl-related temp files in the directory you specify. ๐Ÿ—ƒ๏ธ
  • --check-interval โ€” set the interval (in seconds) of the master checks. โฒ๏ธ
  • --forkbomb-delay โ€” when a forkbomb is detected, sleep for however many seconds you specified. ๐Ÿ›Œ
  • --binary-path โ€” force the binary path. ๐Ÿ›ฃ๏ธ
  • --privileged-binary-patch โ€” patch the uwsgi binary with a new command, and this happens before the privileges drop. ๐Ÿ’…
  • --unprivileged-binary-patch โ€” patch the uwsgi binary with a new command, after the privileges drop. ๐Ÿซถ
  • --privileged-binary-patch-arg โ€” patch the uwsgi binary with a new command and arguments, before the privileges drop. Arguments included, no extra charge. ๐ŸŽ€
  • --unprivileged-binary-patch-arg โ€” patch the uwsgi binary with a new command and arguments, after the privileges drop. ๐ŸŒˆ
  • --async โ€” enable async mode with however many cores you specify. โšก
  • --max-fd โ€” set the maximum number of file descriptors. Heads up: this requires root privileges. ๐Ÿ‘‘
  • --logto โ€” set the logfile/udp address. ๐Ÿชต
  • --logto2 โ€” log to the file or udp address you specify, but after the privileges drop. ๐Ÿซง
  • --log-format โ€” set an advanced format for request logging. Customize your log fit. ๐Ÿ’…
  • --logformat โ€” set advanced format for request logging. The shorter twin. โญ
  • --logformat-strftime โ€” apply strftime to the logformat output. Time stamps, glam edition. ๐Ÿ•ฐ๏ธ
  • --log-format-strftime โ€” apply strftime to the logformat output. Hyphenated twin, same energy. โœจ
  • --logfile-chown โ€” chown the logfiles. ๐Ÿงพ
  • --logfile-chmod โ€” chmod the logfiles. ๐Ÿ”
  • --log-syslog โ€” log to syslog. ๐Ÿ“ฎ
  • --log-socket โ€” send logs to the socket you specify. ๐Ÿ•ณ๏ธ
  • --req-logger โ€” set/append a request logger. ๐Ÿ“
  • --logger-req โ€” set/append a request logger. Yes, it's the same thing with the words swapped. Both real, both listed. ๐Ÿ˜ญ
  • --logger โ€” set/append a logger. The general-purpose one. ๐Ÿช„
  • --logger-list โ€” list the enabled loggers. ๐Ÿ“‹
  • --loggers-list โ€” list the enabled loggers. Plural twins, we stay consistent. ๐Ÿ’–
  • --threaded-logger โ€” offload log writing to a thread. Logs, but make it a background task. ๐Ÿงต
  • --log-encoder โ€” add an item in the log encoder chain. One link at a time. โ›“๏ธ
  • --log-req-encoder โ€” add an item in the log req encoder chain. The request-specific chain. ๐Ÿ”—
  • --log-drain โ€” drain (meaning: do not show) log lines that match the regexp you specify. Swept away, never seen. ๐ŸŒŠ
  • --log-filter โ€” show only the log lines matching the regexp you specify. Cherry-picked. ๐Ÿ’
  • --log-route โ€” log to the named logger you specify, if the regexp applied on the logline matches. Goes to the right place only when it qualifies. ๐Ÿš
  • --log-req-route โ€” log requests to the named logger you specify, if the regexp applied on the logline matches. Request-logging edition. ๐Ÿ“ฌ
  • --use-abort โ€” call abort() on segfault/fpe. The manpage says this could be useful for generating a core dump. ๐Ÿงจ
  • --alarm โ€” create a new alarm. Syntax: <alarm> <plugin:args>. Alarm era, activated. ๐Ÿšจ
  • --alarm-cheap โ€” use the main alarm thread instead of spinning up dedicated threads for curl-based alarms ๐Ÿงต no cap, saves you a whole thread-spawning situation
  • --alarm-freq โ€” tunes the anti-loop alarm system (default 3 seconds) โฐ it's giving "chill, don't spiral"
  • --alarm-fd โ€” raise the specified alarm when an fd is read for read (by default it reads 1 byte, set it to 8 for eventfd) ๐Ÿ‘€
  • --alarm-segfault โ€” raise the specified alarm when the segmentation fault handler is executed ๐Ÿ’€ iconic crash-notification behaviour
  • --segfault-alarm โ€” raise the specified alarm when the segmentation fault handler is executed ๐Ÿ’€ yeah bestie this is the same thing, two names, one vibe
  • --alarm-backlog โ€” raise the specified alarm when the socket backlog queue is full ๐Ÿ˜ญ the queue said "I'm full"
  • --backlog-alarm โ€” raise the specified alarm when the socket backlog queue is full ๐Ÿ˜ญ
  • --lq-alarm โ€” raise the specified alarm when the socket backlog queue is full ๐Ÿ“ฃ
  • --alarm-lq โ€” raise the specified alarm when the socket backlog queue is full ๐Ÿ“ฃ
  • --alarm-listen-queue โ€” raise the specified alarm when the socket backlog queue is full ๐Ÿ””
  • --listen-queue-alarm โ€” raise the specified alarm when the socket backlog queue is full ๐Ÿ””
ok so that backlog thing has six whole aliases and honestly? iconic. pick whichever one your fingers remember.
  • --log-alarm โ€” raise the specified alarm when a log line matches the specified regexp, syntax: <alarm>[,alarm...] <regexp> ๐Ÿ“
  • --alarm-log โ€” raise the specified alarm when a log line matches the specified regexp, syntax: <alarm>[,alarm...] <regexp> ๐Ÿ“
  • --not-log-alarm โ€” skip the specified alarm when a log line matches the specified regexp, syntax: <alarm>[,alarm...] <regexp> ๐Ÿ™…โ€โ™€๏ธ the negation girlie
  • --not-alarm-log โ€” skip the specified alarm when a log line matches the specified regexp, syntax: <alarm>[,alarm...] <regexp> ๐Ÿ™…โ€โ™€๏ธ
  • --alarm-list โ€” list enabled alarms ๐Ÿ“‹โœจ
  • --alarms-list โ€” list enabled alarms ๐Ÿ“‹โœจ (the plural version, we love options)
  • --alarm-msg-size โ€” set the max size of an alarm message (default 8192)

๐Ÿชต the logging era

  • --log-master โ€” delegate logging to the master process ๐Ÿ‘‘
  • --log-master-bufsize โ€” set the buffer size for the master logger. bigger log messages will be truncated โœ‚๏ธ rip to your long logs
  • --log-master-stream โ€” create the master logpipe as SOCK_STREAM ๐ŸŒŠ
  • --log-master-req-stream โ€” create the master requests logpipe as SOCK_STREAM ๐ŸŒŠ
  • --log-reopen โ€” reopen log after reload ๐Ÿ”„
  • --log-truncate โ€” truncate log on startup ๐Ÿ—‘๏ธ fresh start energy
  • --log-maxsize โ€” set maximum logfile size ๐Ÿ“
  • --log-backupname โ€” set logfile name after rotation ๐ŸŒ€
  • --logdate โ€” prefix logs with date or a strftime string ๐Ÿ—“๏ธ
  • --log-date โ€” prefix logs with date or a strftime string ๐Ÿ—“๏ธ
  • --log-prefix โ€” prefix logs with a string ๐Ÿท๏ธ
  • --log-zero โ€” log responses without body ๐Ÿ‘ป empty-body representation
  • --log-slow โ€” log requests slower than the specified number of milliseconds ๐ŸŒโœจ
  • --log-4xx โ€” log requests with a 4xx response
  • --log-5xx โ€” log requests with a 5xx response ๐Ÿ”ฅ
  • --log-big โ€” log requests bigger than the specified size ๐Ÿ˜
  • --log-sendfile โ€” log sendfile requests ๐Ÿ“ค
  • --log-ioerror โ€” log requests with io errors ๐Ÿ’ฅ
  • --log-micros โ€” report response time in microseconds instead of milliseconds โฑ๏ธ tiny numbers, huge precision
  • --log-x-forwarded-for โ€” use the ip from X-Forwarded-For header instead of REMOTE_ADDR ๐ŸŒ

๐Ÿƒ privileges, directories & the working-dir of it all

  • --master-as-root โ€” leave master process running as root ๐Ÿ‘‘โš ๏ธ
  • --drop-after-init โ€” run privileges drop after plugin initialization, superseded by drop-after-apps ๐Ÿ“‰
  • --drop-after-apps โ€” run privileges drop after apps loading, superseded by master-as-root ๐Ÿ“‰
  • --force-cwd โ€” force the initial working directory to the specified value ๐Ÿ“‚
  • --binsh โ€” override /bin/sh (used by exec hooks, it always fallback to /bin/sh) ๐Ÿš
  • --chdir โ€” chdir to specified directory before apps loading ๐Ÿšช
  • --chdir2 โ€” chdir to specified directory after apps loading ๐Ÿšช
  • --lazy โ€” set lazy mode (load apps in workers instead of master) ๐Ÿฆฅ
  • --lazy-apps โ€” load apps in each worker instead of the master ๐Ÿฆฅ
  • --cheap โ€” set cheap mode (spawn workers only after the first request) ๐Ÿ’ธ
  • --cheaper โ€” set cheaper mode (adaptive process spawning) ๐Ÿ“ˆ
  • --cheaper-initial โ€” set the initial number of processes to spawn in cheaper mode ๐Ÿฃ
  • --cheaper-algo โ€” choose to algorithm used for adaptive process spawning ๐Ÿง 
  • --cheaper-step โ€” number of additional processes to spawn at each overload ๐Ÿ’ฅ
  • --cheaper-overload โ€” increase workers after specified overload ๐Ÿš€
  • --cheaper-algo-list โ€” list enabled cheapers algorithms ๐Ÿ“œ
  • --cheaper-algos-list โ€” list enabled cheapers algorithms ๐Ÿ“œ
  • --cheaper-list โ€” list enabled cheapers algorithms ๐Ÿ“œ
  • --cheaper-rss-limit-soft โ€” don't spawn new workers if total resident memory usage of all workers is higher than this limit ๐Ÿง โœ‹
  • --cheaper-rss-limit-hard โ€” if total workers resident memory usage is higher try to stop workers ๐Ÿ›‘
  • --idle โ€” set idle mode (put uWSGI in cheap mode after inactivity) ๐Ÿ˜ด
  • --die-on-idle โ€” shutdown uWSGI when idle โšฐ๏ธ
  • --mount โ€” load application under mountpoint ๐Ÿ—‚๏ธ
  • --worker-mount โ€” load application under mountpoint in the specified worker or after workers spawn ๐Ÿ—‚๏ธ
  • --threads โ€” run each worker in prethreaded mode with the specified number of threads ๐Ÿงตโœจ
  • --thread-stacksize โ€” set threads stacksize ๐Ÿ“š
  • --threads-stacksize โ€” set threads stacksize ๐Ÿ“š
  • --thread-stack-size โ€” set threads stacksize ๐Ÿ“š
  • --threads-stack-size โ€” set threads stacksize ๐Ÿ“š
  • --vhost โ€” enable virtualhosting mode (based on SERVER_NAME variable) ๐Ÿ 
  • --vhost-host โ€” enable virtualhosting mode (based on HTTP_HOST variable) ๐Ÿ 

๐Ÿ›ฃ๏ธ routes, routes & more routes (the whole trilogy)

the regular route girlies

  • --route โ€” add a route ๐Ÿ›ฃ๏ธ
  • --route-host โ€” add a route based on Host header ๐Ÿ“จ
  • --route-uri โ€” add a route based on REQUEST_URI ๐Ÿ”—
  • --route-qs โ€” add a route based on QUERY_STRING โ“
  • --route-remote-addr โ€” add a route based on REMOTE_ADDR ๐ŸŒ
  • --route-user-agent โ€” add a route based on HTTP_USER_AGENT ๐Ÿ•ต๏ธ
  • --route-remote-user โ€” add a route based on REMOTE_USER ๐Ÿ‘ค
  • --route-referer โ€” add a route based on HTTP_REFERER โ†ฉ๏ธ
  • --route-label โ€” add a routing label (for use with goto) ๐Ÿท๏ธ
  • --route-if โ€” add a route based on condition ๐Ÿงฉ
  • --route-if-not โ€” add a route based on condition (negate version) ๐Ÿงฉ๐Ÿ™ƒ
  • --route-run โ€” always run the specified route action โ–ถ๏ธ

final routes (the dramatic finale)

  • --final-route โ€” add a final route ๐Ÿ
  • --final-route-status โ€” add a final route for the specified status ๐Ÿ“Š
  • --final-route-host โ€” add a final route based on Host header ๐Ÿ“จ
  • --final-route-uri โ€” add a final route based on REQUEST_URI ๐Ÿ”—
  • --final-route-qs โ€” add a final route based on QUERY_STRING โ“
  • --final-route-remote-addr โ€” add a final route based on REMOTE_ADDR ๐ŸŒ
  • --final-route-user-agent โ€” add a final route based on HTTP_USER_AGENT ๐Ÿ•ต๏ธ
  • --final-route-remote-user โ€” add a final route based on REMOTE_USER ๐Ÿ‘ค
  • --final-route-referer โ€” add a final route based on HTTP_REFERER โ†ฉ๏ธ
  • --final-route-label โ€” add a final routing label (for use with goto) ๐Ÿท๏ธ
  • --final-route-if โ€” add a final route based on condition ๐Ÿงฉ
  • --final-route-if-not โ€” add a final route based on condition (negate version) ๐Ÿงฉ๐Ÿ™ƒ
  • --final-route-run โ€” always run the specified final route action โ–ถ๏ธ

error routes

  • --error-route โ€” add an error route ๐Ÿšจ
  • --error-route-status โ€” add an error route for the specified status ๐Ÿ“Š
  • --error-route-host โ€” add an error route based on Host header ๐Ÿ“จ
  • --error-route-uri โ€” add an error route based on REQUEST_URI ๐Ÿ”—
  • --error-route-qs โ€” add an error route based on QUERY_STRING โ“
  • --error-route-remote-addr โ€” add an error route based on REMOTE_ADDR ๐ŸŒ
  • --error-route-user-agent โ€” add an error route based on HTTP_USER_AGENT ๐Ÿ•ต๏ธ
  • --error-route-remote-user โ€” add an error route based on REMOTE_USER ๐Ÿ‘ค
  • --error-route-referer โ€” add an error route based on HTTP_REFERER โ†ฉ๏ธ
  • --error-route-label โ€” add an error routing label (for use with goto) ๐Ÿท๏ธ
  • --error-route-if โ€” add an error route based on condition ๐Ÿงฉ
  • --error-route-if-not โ€” add an error route based on condition (negate version) ๐Ÿงฉ๐Ÿ™ƒ
  • --error-route-run โ€” always run the specified error route action โ–ถ๏ธ

response routes

  • --response-route โ€” add a response route ๐Ÿ“ฌ
  • --response-route-status โ€” add a response route for the specified status ๐Ÿ“Š
  • --response-route-host โ€” add a response route based on Host header ๐Ÿ“จ
  • --response-route-uri โ€” add a response route based on REQUEST_URI ๐Ÿ”—
  • --response-route-qs โ€” add a response route based on QUERY_STRING โ“
  • --response-route-remote-addr โ€” add a response route based on REMOTE_ADDR ๐ŸŒ
  • --response-route-user-agent โ€” add a response route based on HTTP_USER_AGENT ๐Ÿ•ต๏ธ
  • --response-route-remote-user โ€” add a response route based on REMOTE_USER ๐Ÿ‘ค
  • --response-route-referer โ€” add a response route based on HTTP_REFERER โ†ฉ๏ธ
  • --response-route-label โ€” add a response routing label (for use with goto) ๐Ÿท๏ธ
  • --response-route-if โ€” add a response route based on condition ๐Ÿงฉ
  • --response-route-if-not โ€” add a response route based on condition (negate version) ๐Ÿงฉ๐Ÿ™ƒ
  • --response-route-run โ€” always run the specified response route action โ–ถ๏ธ
  • --router-list โ€” list enabled routers ๐Ÿ“‹
  • --routers-list โ€” list enabled routers ๐Ÿ“‹
  • --error-page-403 โ€” add an error page (html) for managed 403 response ๐Ÿšซ
  • --error-page-404 โ€” add an error page (html) for managed 404 response ๐Ÿ”
  • --error-page-500 โ€” add an error page (html) for managed 500 response ๐Ÿ’€

๐Ÿฆ‹ websockets & friends

  • --websockets-ping-freq โ€” set the frequency (in seconds) of websockets automatic ping packets ๐Ÿ“
  • --websocket-ping-freq โ€” set the frequency (in seconds) of websockets automatic ping packets ๐Ÿ“
  • --websockets-pong-tolerance โ€” set the tolerance (in seconds) of websockets ping/pong subsystem ๐Ÿ“
  • --websocket-pong-tolerance โ€” set the tolerance (in seconds) of websockets ping/pong subsystem ๐Ÿ“
  • --websockets-max-size โ€” set the max allowed size of websocket messages (in Kbytes, default 1024) ๐Ÿ“ฆ
  • --websocket-max-size โ€” set the max allowed size of websocket messages (in Kbytes, default 1024) ๐Ÿ“ฆ
  • --chunked-input-limit โ€” set the max size of a chunked input part (default 1MB, in bytes) ๐Ÿงฑ
  • --chunked-input-timeout โ€” set default timeout for chunked input โณ
  • --clock โ€” set a clock source โฐ
  • --clock-list โ€” list enabled clocks ๐Ÿ“‹โฐ

okay we're still going through the options list bestie, buckle up ๐Ÿ’…

  • --clocks-list โ€” lists all the enabled clocks โฐ
  • --add-header โ€” automatically adds HTTP headers to the response ๐ŸŽ€
  • --rem-header โ€” automatically removes the HTTP header you named from the response ๐Ÿซฅ
  • --del-header โ€” same energy: automatically removes the specified HTTP header from the response ๐Ÿ™ˆ
  • --collect-header โ€” stashes the specified response header into a request var, syntax is header var ๐Ÿ’พ
  • --response-header-collect โ€” literally the same deal, stores the specified response header in a request var, syntax header var โœจ
  • --pull-header โ€” stores that response header in a request var and rips it out of the response, syntax header var ๐Ÿ”ฅ
  • --check-static โ€” checks for static files in the directory you specify ๐Ÿ“
  • --check-static-docroot โ€” checks for static files in the requested DOCUMENT_ROOT ๐Ÿ 
  • --static-check โ€” yep, again: checks for static files in the directory you specify ๐Ÿ“‚
  • --static-map โ€” maps a mountpoint to a static directory (or a file) ๐Ÿ—บ๏ธ
  • --static-map2 โ€” like static-map but it completely appends the requested resource to the docroot
  • --static-skip-ext โ€” skips the extension you name when doing staticfile checks ๐Ÿšซ
  • --static-index โ€” if a directory gets requested, it searches for the file you specify
  • --static-safe โ€” skips the security checks when the file lives under the path you specify ๐Ÿ›ก๏ธ
  • --static-cache-paths โ€” drops resolved paths into the uWSGI cache for however many seconds you say โณ
  • --static-cache-paths-name โ€” uses the cache you name for static paths
  • --mimefile โ€” sets the mime types file path (default /etc/mime.types) ๐Ÿ“„
  • --mime-file โ€” same thing, sets the mime types file path (default /etc/mime.types)
  • --static-expires-type โ€” sets the Expires header based on content type
  • --static-expires-type-mtime โ€” sets the Expires header based on content type and file mtime
  • --static-expires โ€” sets the Expires header based on filename regexp
  • --static-expires-mtime โ€” sets the Expires header based on filename regexp and file mtime
  • --static-expires-uri โ€” sets the Expires header based on REQUEST_URI regexp
  • --static-expires-uri-mtime โ€” sets the Expires header based on REQUEST_URI regexp and file mtime
  • --static-expires-path-info โ€” sets the Expires header based on PATH_INFO regexp
  • --static-expires-path-info-mtime โ€” sets the Expires header based on PATH_INFO regexp and file mtime
  • --static-gzip โ€” if the regexp you supplied matches the static file translation, it goes looking for a gzip version ๐Ÿ—œ๏ธ
  • --static-gzip-all โ€” checks for a gzip version of all requested static files
  • --static-gzip-dir โ€” checks for a gzip version of all requested static files in the dir/prefix you specify
  • --static-gzip-prefix โ€” checks for a gzip version of all requested static files in the dir/prefix you specify
  • --static-gzip-ext โ€” checks for a gzip version of all requested static files with the ext/suffix you specify
  • --static-gzip-suffix โ€” checks for a gzip version of all requested static files with the ext/suffix you specify
  • --honour-range โ€” enables support for the HTTP Range header ๐Ÿ“
  • --offload-threads โ€” sets how many offload threads to spawn (per-worker, default 0)
  • --offload-thread โ€” sets how many offload threads to spawn (per-worker, default 0)
  • --file-serve-mode โ€” sets the static file serving mode
  • --fileserve-mode โ€” sets the static file serving mode
  • --disable-sendfile โ€” disables sendfile() and makes it rely on boring old read()/write() ๐Ÿ’€
  • --check-cache โ€” checks for response data in the cache you specify (leave it empty for the default cache)
  • --close-on-exec โ€” sets close-on-exec on connection sockets (could be required for spawning processes in requests) ๐Ÿ”’
  • --close-on-exec2 โ€” sets close-on-exec on server sockets (could be required for spawning processes in requests)
  • --mode โ€” sets the uWSGI custom mode
  • --env โ€” sets an environment variable ๐ŸŒฑ
  • --envdir โ€” loads a daemontools compatible envdir
  • --early-envdir โ€” loads a daemontools compatible envdir ASAP โšก
  • --unenv โ€” unsets an environment variable
  • --vacuum โ€” tries to remove all of the generated file/sockets ๐Ÿงน
  • --file-write โ€” writes the content you give to the file you name (syntax: file=value) before the privileges drop โœ๏ธ
  • --cgroup โ€” puts the processes in the cgroup you specify
  • --cgroup-opt โ€” sets a value in the specified cgroup option
  • --cgroup-dir-mode โ€” sets the permission for the cgroup directory (default is 700)
  • --namespace โ€” runs in a new namespace under the rootfs you specify ๐Ÿ“ฆ
  • --namespace-keep-mount โ€” keeps the mountpoint you specify inside your namespace
  • --ns โ€” runs in a new namespace under the rootfs you specify
  • --namespace-net โ€” adds a network namespace ๐ŸŒ
  • --ns-net โ€” adds a network namespace
  • --enable-proxy-protocol โ€” enables PROXY1 protocol support (only for http parsers!) ๐ŸŽฏ
  • --reuse-port โ€” enables the REUSE_PORT flag on the socket (BSD only) ๐ŸŽ
  • --tcp-fast-open โ€” enables the TCP_FASTOPEN flag on TCP sockets with the qlen value you give
  • --tcp-fastopen โ€” enables the TCP_FASTOPEN flag on TCP sockets with the qlen value you give
  • --tcp-fast-open-client โ€” uses sendto(..., MSG_FASTOPEN, ...) instead of connect() if it's supported ๐Ÿš€
  • --tcp-fastopen-client โ€” uses sendto(..., MSG_FASTOPEN, ...) instead of connect() if it's supported
  • --zerg โ€” attaches to a zerg server ๐Ÿ›
  • --zerg-fallback โ€” falls back to normal sockets if the zerg server isn't available
  • --zerg-server โ€” enables the zerg server on the UNIX socket you specify
  • --cron โ€” adds a cron task โฒ๏ธ
  • --cron2 โ€” adds a cron task (key=val syntax)
  • --unique-cron โ€” adds a unique cron task
  • --cron-harakiri โ€” sets the maximum time (in seconds) we wait for a cron command to complete โŒ›
  • --legion-cron โ€” adds a cron task that's runnable only when the instance is a lord of the legion you specify ๐Ÿ‘‘
  • --cron-legion โ€” adds a cron task that's runnable only when the instance is a lord of the legion you specify
  • --unique-legion-cron โ€” adds a unique cron task runnable only when the instance is a lord of the legion you specify
  • --unique-cron-legion โ€” adds a unique cron task runnable only when the instance is a lord of the legion you specify
  • --loop โ€” selects the uWSGI loop engine ๐Ÿ”
  • --loop-list โ€” lists the enabled loop engines
  • --loops-list โ€” lists the enabled loop engines
  • --worker-exec โ€” runs the command you specify as a worker ๐Ÿ”ง
  • --worker-exec2 โ€” runs the command you specify as a worker (after the post_fork hook)
  • --attach-daemon โ€” attaches a command/daemon to the master process (heads up: the command has to not go in the background!)
  • --attach-control-daemon โ€” attaches a command/daemon to the master process (the command has to not go in background), and when the daemon dies, the master dies too ๐Ÿ’€
  • --smart-attach-daemon โ€” attaches a command/daemon to the master process managed by a pidfile (the command has to daemonize)
  • --smart-attach-daemon2 โ€” attaches a command/daemon to the master process managed by a pidfile (the command has to NOT daemonize)
  • --legion-attach-daemon โ€” same as --attach-daemon but the daemon only runs on the legion lord node ๐Ÿ‘‘
  • --legion-smart-attach-daemon โ€” same as --smart-attach-daemon but the daemon runs only on the legion lord node
  • --legion-smart-attach-daemon2 โ€” same as --smart-attach-daemon2 but the daemon runs only on the legion lord node
  • --daemons-honour-stdin โ€” doesn't change the stdin of external daemons to /dev/null ๐Ÿซถ
  • --attach-daemon2 โ€” the attach-daemon keyval variant (supports smart modes too)
  • --plugins โ€” loads uWSGI plugins ๐Ÿ”Œ
  • --plugin โ€” loads uWSGI plugins
  • --need-plugins โ€” loads uWSGI plugins (exits on error) ๐Ÿšจ
  • --need-plugin โ€” loads uWSGI plugins (exits on error)
  • --plugins-dir โ€” adds a directory to the uWSGI plugin search path ๐Ÿ—‚๏ธ
  • --plugin-dir โ€” adds a directory to the uWSGI plugin search path
  • --plugins-list โ€” lists the enabled plugins
  • --plugin-list โ€” lists the enabled plugins
  • --autoload โ€” tries to automatically load plugins when unknown options are found ๐Ÿ•ต๏ธ
  • --dlopen โ€” blindly loads a shared library ๐Ÿ™ˆ
  • --allowed-modifiers โ€” comma separated list of the allowed modifiers
  • --remap-modifier โ€” remaps a request modifier from one id to another
  • --dump-options โ€” dumps the full list of available options ๐Ÿ—’๏ธ
  • --show-config โ€” shows the current config reformatted as ini โœจ
  • --binary-append-data โ€” returns the content of a resource to stdout for appending to a uwsgi binary (for data:// usage)
  • --print โ€” a simple print ๐Ÿ–จ๏ธ
  • --iprint โ€” a simple print, but the immediate version โšก
  • --exit โ€” forces exit() of the instance ๐Ÿšช
  • --cflags โ€” reports the uWSGI CFLAGS (super useful for building external plugins) ๐Ÿ› ๏ธ
  • --dot-h โ€” dumps the uwsgi.h used for building the core (useful for building external plugins)
  • --config-py โ€” dumps the uwsgiconfig.py used for building the core (useful for building external plugins)
  • --build-plugin โ€” builds a uWSGI plugin for the current binary ๐Ÿ—๏ธ
  • --version โ€” prints the uWSGI version ๐Ÿท๏ธ
  • --response-headers-limit โ€” sets the response header maximum size (default: 64k)

and that's the whole thing bestie, you made it to the end ๐ŸŽ‰ this page is from uwsgi_alarm_curl version 2.0.31-debian, dated July 2026, and it's the UWSGI_ALARM_CURL(1) manual page ๐Ÿซถ now go configure something iconic, mwah ๐Ÿ’…๐Ÿ’–

๐Ÿ“ฆ where this page comes from