description

# File lib/rubygems/commands/environment_command.rb, line 23
  def description # :nodoc:
    The environment command lets you query rubygems for its configuration foruse in shell scripts or as a debugging aid.The RubyGems environment can be controlled through command line arguments,gemrc files, environment variables and built-in defaults.Command line argument defaults and some RubyGems defaults can be set in a~/.gemrc file for individual users and a gemrc in the SYSTEM CONFIGURATIONDIRECTORY for all users. These files are YAML files with the following YAMLkeys:  :sources: A YAML array of remote gem repositories to install gems from  :verbose: Verbosity of the gem command. false, true, and :really are the            levels  :update_sources: Enable/disable automatic updating of repository metadata  :backtrace: Print backtrace when RubyGems encounters an error  :gempath: The paths in which to look for gems  :disable_default_gem_server: Force specification of gem server host on push  <gem_command>: A string containing arguments for the specified gem commandExample:  :verbose: false  install: --no-wrappers  update: --no-wrappers  :disable_default_gem_server: trueRubyGems' default local repository can be overridden with the GEM_PATH andGEM_HOME environment variables. GEM_HOME sets the default repository toinstall into. GEM_PATH allows multiple local repositories to be searched forgems.If you are behind a proxy server, RubyGems uses the HTTP_PROXY,HTTP_PROXY_USER and HTTP_PROXY_PASS environment variables to discover theproxy server.If you would like to push gems to a private gem server the RUBYGEMS_HOSTenvironment variable can be set to the URI for that server.If you are packaging RubyGems all of RubyGems' defaults are inlib/rubygems/defaults.rb.  You may override these inlib/rubygems/defaults/operating_system.rb
  end