gems-client(1) [debian man page]

GEMS-CLIENT(1)							gems documentation						    GEMS-CLIENT(1)

NAME

       gems-client - Show data transmitted by gems-server (1)

SYNOPSIS

       gems-client [-i] host [port]

       gems-client -h | -v

DESCRIPTION

       Connects to a computer running gems-server(1) to show in the local terminal the data transmitted, in real time.

OPTIONS

       host   Hostname or IP address where the server is running.

       port   TCP port used by the server. Default: 6666.

       -i     Ignore  server  terminal size. If this option is not supplied, gems-client disconnects itself whenever the local terminal is smaller
	      than the terminal associated to the server.

       -h     Show a short help message.

       -v     Show version information.

FUNCTION KEYS

       While gems-client is running, some keys have special functions:

       q      Quit.

       a      Enable/disable alarm blocking. When active, if the server transmits an alarm character ('a'), the client ignores it, so	the  alarm
	      does not play. This is specially useful when many clients are present in the same room, to avoid the annoying simultaneous beeps.

AUTHORS

       Diego Essaya <dessaya@fi.uba.ar>

       Emiliano Castagnari <ecastag@fi.uba.ar>

SEE ALSO

       gems-server(1), script(1)

gems								    AUGUST 2004 						    GEMS-CLIENT(1)

BUNDLE-PACKAGE(1)														 BUNDLE-PACKAGE(1)

NAME

       bundle-package - Package your needed .gem files into your application

SYNOPSIS

       bundle package

DESCRIPTION

       Copy  all  of  the  .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1)
       bundle-install.1.html, use the gems in the cache in preference to the ones on rubygems.org.

GIT AND PATH GEMS

       In Bundler 1.0, the bundle package command only packages .gem files, not gems specified using the :git or :path options. This  will  likely
       change in the future.

REMOTE FETCHING

       By  default,  if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
       still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.

       For instance, consider this Gemfile(5):

	   source "http://rubygems.org"

	   gem "nokogiri"

       If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to	JRuby  and
       run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.

       Even  though  the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
       JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
       cific to your platform.

       This  problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
       ing to Linux, or even when developing on OSX and deploying to Linux.

       If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
       to skip checking for more appropriate gems, and just use the ones in vendor/cache.

       One  way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
       in the gems. For instance, you can run bundle package on an identical staging box during your  staging  process,  and  check  in  the  ven-
       dor/cache before deploying to production.

								     June 2012							 BUNDLE-PACKAGE(1)