Linux cesa-www-main 6.1.0-49-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64
Apache/2.4.68 (Debian)
Server IP : 10.218.0.2 & Your IP : 216.73.216.28
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
lib /
ruby /
3.1.0 /
bundler /
man /
Delete
Unzip
Name
Size
Permission
Date
Action
bundle-add.1
1.61
KB
-rw-r--r--
2022-04-12 11:11
bundle-add.1.ronn
1.36
KB
-rw-r--r--
2022-04-12 11:11
bundle-binstubs.1
1.58
KB
-rw-r--r--
2022-04-12 11:11
bundle-binstubs.1.ronn
1.38
KB
-rw-r--r--
2022-04-12 11:11
bundle-cache.1
3.19
KB
-rw-r--r--
2022-04-12 11:11
bundle-cache.1.ronn
2.87
KB
-rw-r--r--
2022-04-12 11:11
bundle-check.1
966
B
-rw-r--r--
2022-04-12 11:11
bundle-check.1.ronn
857
B
-rw-r--r--
2022-04-12 11:11
bundle-clean.1
604
B
-rw-r--r--
2022-04-12 11:11
bundle-clean.1.ronn
484
B
-rw-r--r--
2022-04-12 11:11
bundle-config.1
20.89
KB
-rw-r--r--
2022-04-12 11:11
bundle-config.1.ronn
18.5
KB
-rw-r--r--
2022-04-12 11:11
bundle-doctor.1
1.14
KB
-rw-r--r--
2022-04-12 11:11
bundle-doctor.1.ronn
975
B
-rw-r--r--
2022-04-12 11:11
bundle-exec.1
6.6
KB
-rw-r--r--
2022-04-12 11:11
bundle-exec.1.ronn
5.87
KB
-rw-r--r--
2022-04-12 11:11
bundle-gem.1
5.02
KB
-rw-r--r--
2022-04-12 11:11
bundle-gem.1.ronn
4.52
KB
-rw-r--r--
2022-04-12 11:11
bundle-info.1
449
B
-rw-r--r--
2022-04-12 11:11
bundle-info.1.ronn
369
B
-rw-r--r--
2022-04-12 11:11
bundle-init.1
1.05
KB
-rw-r--r--
2022-04-12 11:11
bundle-init.1.ronn
939
B
-rw-r--r--
2022-04-12 11:11
bundle-inject.1
738
B
-rw-r--r--
2022-04-12 11:11
bundle-inject.1.ronn
597
B
-rw-r--r--
2022-04-12 11:11
bundle-install.1
17.6
KB
-rw-r--r--
2022-04-12 11:11
bundle-install.1.ronn
16.57
KB
-rw-r--r--
2022-04-12 11:11
bundle-list.1
965
B
-rw-r--r--
2022-04-12 11:11
bundle-list.1.ronn
788
B
-rw-r--r--
2022-04-12 11:11
bundle-lock.1
3.12
KB
-rw-r--r--
2022-04-12 11:11
bundle-lock.1.ronn
2.97
KB
-rw-r--r--
2022-04-12 11:11
bundle-open.1
581
B
-rw-r--r--
2022-04-12 11:11
bundle-open.1.ronn
442
B
-rw-r--r--
2022-04-12 11:11
bundle-outdated.1
3.72
KB
-rw-r--r--
2022-04-12 11:11
bundle-outdated.1.ronn
3.46
KB
-rw-r--r--
2022-04-12 11:11
bundle-platform.1
1.31
KB
-rw-r--r--
2022-04-12 11:11
bundle-platform.1.ronn
1.12
KB
-rw-r--r--
2022-04-12 11:11
bundle-pristine.1
1.64
KB
-rw-r--r--
2022-04-12 11:11
bundle-pristine.1.ronn
1.46
KB
-rw-r--r--
2022-04-12 11:11
bundle-remove.1
849
B
-rw-r--r--
2022-04-12 11:11
bundle-remove.1.ronn
730
B
-rw-r--r--
2022-04-12 11:11
bundle-show.1
690
B
-rw-r--r--
2022-04-12 11:11
bundle-show.1.ronn
596
B
-rw-r--r--
2022-04-12 11:11
bundle-update.1
13.58
KB
-rw-r--r--
2022-04-12 11:11
bundle-update.1.ronn
12.5
KB
-rw-r--r--
2022-04-12 11:11
bundle-viz.1
1.08
KB
-rw-r--r--
2022-04-12 11:11
bundle-viz.1.ronn
958
B
-rw-r--r--
2022-04-12 11:11
bundle.1
3.51
KB
-rw-r--r--
2022-04-12 11:11
bundle.1.ronn
3.07
KB
-rw-r--r--
2022-04-12 11:11
gemfile.5
21.69
KB
-rw-r--r--
2022-04-12 11:11
gemfile.5.ronn
19.76
KB
-rw-r--r--
2022-04-12 11:11
Save
Rename
bundle-pristine(1) -- Restores installed gems to their pristine condition =========================================================================== ## SYNOPSIS `bundle pristine` ## DESCRIPTION `pristine` restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems. For git gems, a forced checkout will be performed. For further explanation, `bundle pristine` ignores unpacked files on disk. In other words, this command utilizes the local `.gem` cache or the gem's git repository as if one were installing from scratch. Note: the Bundler gem cannot be restored to its original state with `pristine`. One also cannot use `bundle pristine` on gems with a 'path' option in the Gemfile, because bundler has no original copy it can restore from. When is it practical to use `bundle pristine`? It comes in handy when a developer is debugging a gem. `bundle pristine` is a great way to get rid of experimental changes to a gem that one may not want. Why use `bundle pristine` over `gem pristine --all`? Both commands are very similar. For context: `bundle pristine`, without arguments, cleans all gems from the lockfile. Meanwhile, `gem pristine --all` cleans all installed gems for that Ruby version. If a developer forgets which gems in their project they might have been debugging, the Rubygems `gem pristine [GEMNAME]` command may be inconvenient. One can avoid waiting for `gem pristine --all`, and instead run `bundle pristine`.