jc00ke/guard-puma

Issues

• Problem running guard-puma in docker

  #46 opened 3 years ago by Zetrs
  8

• Rework logic in detecting default config file

  #39 opened 6 years ago by jc00ke
  0

• Crash if config/puma.rb is missing

  #38 opened 6 years ago by jodosha
  6

• Default Puma config location in Rails 5.2 crashes on start

  #36 opened 6 years ago by matoakley
  6

• Puma should be quiet by default? Expose config?

  #24 opened 7 years ago by ioquatix
  3

• Use securerandom for control token

  #23 opened 8 years ago by ioquatix
  18

• If puma crashes for some reason, it would never be restarted

  #22 opened 8 years ago by ioquatix
  1

• Environment option broken

  #21 opened 8 years ago by ealders
  4

• When using config file, exiting guard doesn't kill puma

  #18 opened 8 years ago by dsandstrom
  4

• Starting shouldn't report Restarting

  #2 opened 8 years ago by jc00ke
  1

• Doesn't use port specifed in config

  #17 opened 8 years ago by dsandstrom
  3

• guard-puma depends on rb-inotify and libnotify even though it doesn't use them

  #11 opened 10 years ago by ressu
  0

• Killing guard doesn't kill puma

  #6 opened 11 years ago by drnic
  17

• should app/ be part of the default watch?

  #4 opened 13 years ago by stve
  3

• Use the state file to allow faster/better restarts

  #5 opened 13 years ago by docwhat
  2

• Support the other CLI options

  #1 opened 13 years ago by jc00ke
  0

• Daemonize or redirect log output

  #3 opened 13 years ago by jc00ke
  0