PUMA(1)

πŸ’– NAME πŸ’–

okay so bestie, pumactl β€” that's the command line client for puma. that's the whole vibe. it's how you talk to your puma server without, like, touching it directly. iykyk ✨


🌸 USAGE 🌸

here's the shape of it, fr fr:

pumactl [options...] [commands]

and if you just wanna vibe-check it:

pumactl [-h | --help | -V | --version]

πŸŽ€ COMMANDS πŸŽ€

these are the moves, bestie. pick one. πŸ’…

  • halt β€” halt the server. like, full stop. no notes.
  • restart β€” restart the server. iconic, classic, we love her.
  • phased-restart β€” restart the server but do it ✨gracefully✨: it phases out the old workers while starting up new workers one at a time. no chaos, just vibes.
  • start β€” start the server. get her going.
  • stats β€” show stats about the server. the receipts, basically.
  • status β€” show server status. is she okay? let's find out.
  • stop β€” stop the server. bye bestie 🫢
  • reload-worker-directory β€” reload the worker directory. simple as that.
  • gc β€” start the garbage collector. she's cleaning up, periodt.
  • gc-stats β€” show information about the garbage collector. the cleanup receipts. πŸ’€

✨ OPTIONS ✨

the following options are available, and yes you need to know all of them, no skipping πŸ™ˆ:

  • -F, --config-file PATH β€” load the given path as a config file. feed her the file, she'll read it.
  • -T, --control-token TOKEN β€” the TOKEN to use as authentication for the control server. it's the password, basically, so guard it.
  • -C, --control-url URL β€” the bind URL to use for the control server and app. use auto to use a temp unix server. > ⚠️ this requires you to use a --control-token, and that token needs to be given with every request to the control server β€” like token=foo. no token, no entry, no cap.
  • -p, --pid PID β€” define the TCP port to bind to. use -b for more advanced options.
  • -P, --pidfile PATH β€” use the given path as PID file. that's where the pid lives.
  • -Q, --quiet β€” don't display messages. silence, but make it intentional. 🀫
  • -S, --state PATH β€” where the state file is. point her at it.
  • -H, --help β€” show help. when in doubt, ask for help bestie, it's free.
  • -V, --version β€” print the version information. so you know exactly what you're working with. πŸ’–

πŸ¦‹ EXAMPLES πŸ¦‹

okay so here's the main character moment: create a control server, then use pumactl(1) to interact with the control server and restart puma. literally the whole point. ⭐

puma --control-url tcp://127.0.0.1:9293 --control-token foo
pumactl --control-url 'tcp://127.0.0.1:9293' --control-token foo
restart

see how the token foo shows up both times? that's the vibe. 🌈


πŸ‘‘ SEE ALSO πŸ‘‘

  • puma(1) β€” the main character herself.

there is extensive documentation at <https://puma.io/puma/> and <https://github.com/puma/puma>. go read it, i'm begging 🧚


πŸ’œ AUTHOR πŸ’œ

this manual page was written by Daniel Leidert <dleidert@debian.org>, for the Debian GNU/Linux system (but may be used by others). king behavior honestly. πŸ‘‘


and that's the whole page bestie β€” this is PUMA 3.12, dated January 2020, and it ate, no crumbs. slay πŸ’…πŸŽ€πŸ’–