puma--puma/test/config/prune_bundler_with_deps.rb

prune_bundler true
extra_runtime_dependencies ["rdoc"]
before_fork do
  $LOAD_PATH.each do |path|
    puts "LOAD_PATH: #{path}"
  end
end
Allow extra runtime deps to be defined when using prune_bundler (#1105) * Allow extra runtime deps to be defined when using prune_bundler * Check extra_runtime_dependencies is set before iterating over them * Load additional paths for extra runtime dep gems * Don't load extra dependencies, just add their paths to $LOAD_PATH * Fix typos and extraneous checks and rescues * Use Gem::Specification#full_require_paths when available * Prevent use of prune_bundler and extra_runtime_dependencies with early versions of RubyGems * Ensure LOAD_PATH is modified by extra_runtime_dependencies * Refactor prune_bundler in launcher.rb and write some unit tests 2019-09-02 12:10:33 -04:00			`prune_bundler true`
			`extra_runtime_dependencies ["rdoc"]`
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			`before_fork do`
			`$LOAD_PATH.each do \|path\|`
			`puts "LOAD_PATH: #{path}"`
			`end`
			`end`