Offline RubyGems Installs Need the Full Dependency Set

A browser-downloaded .gem can get past the original proxy problem without making the installation self-contained. Before moving the archive to the target, prepare:

• Suitable versions of every missing declared dependency.
• Archives compatible with the target Ruby, RubyGems and platform.
• Compilers, headers and system libraries needed by any native extensions.

Ask RubyGems for local installation explicitly:

gem install ./example-1.2.3.gem --local

Replace the example filename. Resolve missing material through the approved artifact process rather than disabling dependency checks. A platform build from another machine may not work just because its name and version match.

Local mode concerns RubyGems' fetch behavior. Extension build scripts can do other work, so it is not a sandbox for arbitrary installation code. An extension failure can indicate a missing build prerequisite after the archive has already arrived; report that stage separately from a proxy refusal.

For repeat deployments, maintain the dependency set through the project's normal packaging workflow. Otherwise changes in dependency versions or architecture can turn the next ad hoc browser download into a different installation.