puma--puma/bin/puma-wild

#!/usr/bin/env ruby
#
# Copyright (c) 2014 Evan Phoenix
#

require 'rubygems'

cli_arg = ARGV.shift

inc = ""

if cli_arg == "-I"
  inc = ARGV.shift
  $LOAD_PATH.concat inc.split(":")
end

module Puma; end

Puma.const_set("WILD_ARGS", ["-I", inc])

require 'puma/cli'

cli = Puma::CLI.new ARGV

cli.run
Push through rack dep into the wild puma 2014-03-03 14:13:29 -05:00			`#!/usr/bin/env ruby`
			`#`
			`# Copyright (c) 2014 Evan Phoenix`
			`#`

			`require 'rubygems'`

Fix Bundler::GemNotFound errors for nio4r gem (#2427) * Update extra_runtime_dependencies test to test master proccess's gems The `extra_runtime_dependencies` option allows one to activate gems in the puma master process after "pruning" the master process with `prune_bundler`. This is useful for activating gems that need to be loaded in the master process, such as `puma_worker_killer`. The integration test for `extra_runtime_dependencies` tested the `$LOAD_PATH` of the worker process instead. Since workers are forked from the master, it's normally fine to do this, but we might as well test the master process's `$LOAD_PATH` directly if we can. * Add test to refute that nio4r is loaded into puma master process * Remove nio4r from puma master $LOAD_PATH * Remove list of gems to activate from puma-wild * Update History.md Co-authored-by: Nate Berkopec <nate.berkopec@gmail.com> 2020-10-20 09:31:23 -04:00			`cli_arg = ARGV.shift`
Fix puma-wild handling a restart properly. Fixes #550 2014-10-29 20:07:25 -04:00
			`inc = ""`

Fix Bundler::GemNotFound errors for nio4r gem (#2427) * Update extra_runtime_dependencies test to test master proccess's gems The `extra_runtime_dependencies` option allows one to activate gems in the puma master process after "pruning" the master process with `prune_bundler`. This is useful for activating gems that need to be loaded in the master process, such as `puma_worker_killer`. The integration test for `extra_runtime_dependencies` tested the `$LOAD_PATH` of the worker process instead. Since workers are forked from the master, it's normally fine to do this, but we might as well test the master process's `$LOAD_PATH` directly if we can. * Add test to refute that nio4r is loaded into puma master process * Remove nio4r from puma master $LOAD_PATH * Remove list of gems to activate from puma-wild * Update History.md Co-authored-by: Nate Berkopec <nate.berkopec@gmail.com> 2020-10-20 09:31:23 -04:00			`if cli_arg == "-I"`
Fix puma-wild handling a restart properly. Fixes #550 2014-10-29 20:07:25 -04:00			`inc = ARGV.shift`
			`$LOAD_PATH.concat inc.split(":")`
Push through rack dep into the wild puma 2014-03-03 14:13:29 -05:00			`end`

Fix puma-wild handling a restart properly. Fixes #550 2014-10-29 20:07:25 -04:00			`module Puma; end`

Fix Bundler::GemNotFound errors for nio4r gem (#2427) * Update extra_runtime_dependencies test to test master proccess's gems The `extra_runtime_dependencies` option allows one to activate gems in the puma master process after "pruning" the master process with `prune_bundler`. This is useful for activating gems that need to be loaded in the master process, such as `puma_worker_killer`. The integration test for `extra_runtime_dependencies` tested the `$LOAD_PATH` of the worker process instead. Since workers are forked from the master, it's normally fine to do this, but we might as well test the master process's `$LOAD_PATH` directly if we can. * Add test to refute that nio4r is loaded into puma master process * Remove nio4r from puma master $LOAD_PATH * Remove list of gems to activate from puma-wild * Update History.md Co-authored-by: Nate Berkopec <nate.berkopec@gmail.com> 2020-10-20 09:31:23 -04:00			`Puma.const_set("WILD_ARGS", ["-I", inc])`
Fix puma-wild handling a restart properly. Fixes #550 2014-10-29 20:07:25 -04:00
Push through rack dep into the wild puma 2014-03-03 14:13:29 -05:00			`require 'puma/cli'`

			`cli = Puma::CLI.new ARGV`

			`cli.run`