So finden Sie heraus, wo Gem-Dateien installiert sind

Ich fand es nützlich, den Speicherort der Bibliotheksdatei zu ermitteln mit:

gem which *gemname*

Wenn Sie nach dem Installieren der Edelsteine ​​wissen möchten, wo sich ein bestimmter Edelstein befindet. Versuchen Sie Folgendes einzugeben:

 gem list

Sie können die Liste der Edelsteine ​​sehen, die Sie installiert haben. Verwenden Sie nun bundle show und benennen Sie den Edelstein, für den Sie den Pfad kennen möchten, wie folgt:

 bundle show <gemName>

Um andere Antworten zu vervollständigen, kann der gem-path gem den Installationspfad eines bestimmten Gems finden.

Installation:

gem install gem-path

Verwendungszweck:

gem path Rails
=> /home/cbliard/.rvm/gems/Ruby-2.1.5/gems/Rails-4.0.13
gem path Rails '< 4'
=> /home/cbliard/.rvm/gems/Ruby-2.1.5/gems/Rails-3.2.21

Dies ist sehr praktisch, da Sie damit Dateien suchen oder bearbeiten können:

grep -R 'Internal server error' "$(gem path thin)"
subl "$(gem path thin)"

Sie können dies über die Eingabeaufforderung überprüfen, indem Sie gem help commands ausführen und dann den richtigen Befehl auswählen:

[email protected]:~$  gem help commands
GEM commands are:

    build                  Build a gem from a gemspec
    cert                   Manage RubyGems certificates and signing settings
    check                  Check a gem repository for added or missing files
    cleanup                Clean up old versions of installed gems in the local
                           repository
    contents               Display the contents of the installed gems
    dependency             Show the dependencies of an installed gem
    environment            Display information about the RubyGems environment
    fetch                  Download a gem and place it in the current directory
    generate_index         Generates the index files for a gem server directory
    help                   Provide help on the 'gem' command
    install                Install a gem into the local repository
    list                   Display gems whose name starts with STRING
    lock                   Generate a lockdown list of gems
    mirror                 Mirror all gem files (requires rubygems-mirror)
    outdated               Display all gems that need updates
    owner                  Manage gem owners on RubyGems.org.
    pristine               Restores installed gems to pristine condition from
                           files located in the gem cache
    Push                   Push a gem up to RubyGems.org
    query                  Query gem information in local or remote repositories
    rdoc                   Generates RDoc for pre-installed gems
    regenerate_binstubs    Re run generation of executable wrappers for gems.
    search                 Display all gems whose name contains STRING
    server                 Documentation and gem repository HTTP server
    sources                Manage the sources and cache file RubyGems uses to
                           search for gems
    specification          Display gem specification (in yaml)
    stale                  List gems along with access times
    uninstall              Uninstall gems from the local repository
    unpack                 Unpack an installed gem to the current directory
    update                 Update installed gems to the latest version
    which                  Find the location of a library file you can require
    yank                   Remove a specific gem version release from
                           RubyGems.org

For help on a particular command, use 'gem help COMMAND'.

Commands may be abbreviated, so long as they are unambiguous.
e.g. 'gem i rake' is short for 'gem install rake'.
[email protected]:~$ 

Jetzt kann ich von oben sehen, dass der Befehl environment hilfreich ist. Also würde ich tun:

[email protected]:~$ gem help environment
Usage: gem environment [arg] [options]


  Common Options:
    -h, --help                       Get help on this command
    -V, --[no-]verbose               Set the verbose level of output
    -q, --quiet                      Silence commands
        --config-file FILE           Use this config file instead of default
        --backtrace                  Show stack backtrace on errors
        --debug                      Turn on Ruby debugging


  Arguments:
    packageversion  display the package version
    gemdir          display the path where gems are installed
    gempath         display path used to search for gems
    version         display the gem format version
    remotesources   display the remote gem servers
    platform        display the supported gem platforms
    <omitted>       display everything

  Summary:
    Display information about the RubyGems environment

  Description:
    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 /etc/gemrc for all users. These
    files are YAML files with the following YAML keys:

      :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 command

    Example:

      :verbose: false
      install: --no-wrappers
      update: --no-wrappers
      :disable_default_gem_server: true

    RubyGems' default local repository can be overridden with the GEM_PATH and
    GEM_HOME environment variables. GEM_HOME sets the default repository to
    install into. GEM_PATH allows multiple local repositories to be searched for
    gems.

    If you are behind a proxy server, RubyGems uses the HTTP_PROXY,
    HTTP_PROXY_USER and HTTP_PROXY_PASS environment variables to discover the
    proxy server.

    If you would like to Push gems to a private gem server the RUBYGEMS_Host
    environment variable can be set to the URI for that server.

    If you are packaging RubyGems all of RubyGems' defaults are in
    lib/rubygems/defaults.rb.  You may override these in
    lib/rubygems/defaults/operating_system.rb
[email protected]:~$ 

Um Ihnen zu zeigen, was Sie gefragt haben, würde ich Folgendes tun:

[email protected]:~$ gem environment gemdir
/home/kirti/.rvm/gems/Ruby-2.0.0-p0
[email protected]:~$ gem environment gempath
/home/kirti/.rvm/gems/Ruby-2.0.0-p0:/home/kirti/.rvm/gems/[email protected]
[email protected]:~$ 

gem env funktioniert genau wie gem environment. Spart etwas Tipparbeit.

# gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 2.0.14
  - Ruby VERSION: 2.0.0 (2014-02-24 patchlevel 451) [i686-linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/Ruby/gems/2.0.0
  - Ruby EXECUTABLE: /usr/local/bin/Ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - Ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/Ruby/gems/2.0.0
     - /root/.gem/Ruby/2.0.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - https://rubygems.org/

Sie können gem open überlisten, um den Edelsteinpfad anzuzeigen:

VISUAL=echo gem open gem-name

Beispiel:

VISUAL=echo gem open Rails
=> /usr/local/opt/asdf/installs/Ruby/2.4.3/lib/Ruby/gems/2.4.0/gems/Rails-5.1.4

Ich vermute, dass rvm (und rbenv) den Pfad zu gem home in eine Umgebungsvariable speichern. Wenn ich renne

env | grep GEM_

Ich bekomme

• GEM_HOME=/Users/Me/.rvm/gems/[email protected]_project
• GEM_PATH=/Users/Me/.rvm/gems/[email protected]_project: /Users/Me/.rvm/gems/[email protected]_project

Ich denke, dass $ GEM_HOME der Ort ist, an dem Sie interessiert sind

Die Edelsteine ​​werden in $ GEM_HOME "/ gems" installiert.