gemstash 2.1.0 → 2.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +57 -0
  3. data/lib/gemstash/cache.rb +37 -0
  4. data/lib/gemstash/cli/authorize.rb +2 -2
  5. data/lib/gemstash/cli/setup.rb +11 -3
  6. data/lib/gemstash/configuration.rb +1 -1
  7. data/lib/gemstash/dependencies.rb +2 -2
  8. data/lib/gemstash/env.rb +2 -0
  9. data/lib/gemstash/gem_fetcher.rb +2 -2
  10. data/lib/gemstash/gem_pusher.rb +2 -2
  11. data/lib/gemstash/gem_source/private_source.rb +3 -3
  12. data/lib/gemstash/gem_source.rb +2 -2
  13. data/lib/gemstash/http_client.rb +8 -3
  14. data/lib/gemstash/logging.rb +1 -1
  15. data/lib/gemstash/man/gemstash-authorize.1.txt +0 -45
  16. data/lib/gemstash/man/gemstash-configuration.5.txt +0 -209
  17. data/lib/gemstash/man/gemstash-customize.7.txt +0 -186
  18. data/lib/gemstash/man/gemstash-debugging.7.txt +0 -28
  19. data/lib/gemstash/man/gemstash-deploy.7.txt +0 -58
  20. data/lib/gemstash/man/gemstash-mirror.7.txt +0 -32
  21. data/lib/gemstash/man/gemstash-multiple-sources.7.txt +0 -70
  22. data/lib/gemstash/man/gemstash-private-gems.7.txt +0 -155
  23. data/lib/gemstash/man/gemstash-readme.7.txt +0 -181
  24. data/lib/gemstash/man/gemstash-setup.1.txt +0 -39
  25. data/lib/gemstash/man/gemstash-start.1.txt +0 -25
  26. data/lib/gemstash/man/gemstash-status.1.txt +0 -21
  27. data/lib/gemstash/man/gemstash-stop.1.txt +0 -21
  28. data/lib/gemstash/man/gemstash-version.1.txt +0 -20
  29. data/lib/gemstash/storage.rb +5 -4
  30. data/lib/gemstash/upstream.rb +6 -5
  31. data/lib/gemstash/version.rb +2 -2
  32. data/lib/gemstash/web.rb +6 -4
  33. data/lib/gemstash.rb +1 -1
  34. metadata +31 -171
  35. data/lib/gemstash/man/gemstash-authorize.1 +0 -51
  36. data/lib/gemstash/man/gemstash-configuration.5 +0 -229
  37. data/lib/gemstash/man/gemstash-customize.7 +0 -301
  38. data/lib/gemstash/man/gemstash-debugging.7 +0 -34
  39. data/lib/gemstash/man/gemstash-deploy.7 +0 -72
  40. data/lib/gemstash/man/gemstash-mirror.7 +0 -40
  41. data/lib/gemstash/man/gemstash-multiple-sources.7 +0 -89
  42. data/lib/gemstash/man/gemstash-private-gems.7 +0 -227
  43. data/lib/gemstash/man/gemstash-readme.7 +0 -233
  44. data/lib/gemstash/man/gemstash-setup.1 +0 -43
  45. data/lib/gemstash/man/gemstash-start.1 +0 -26
  46. data/lib/gemstash/man/gemstash-status.1 +0 -20
  47. data/lib/gemstash/man/gemstash-stop.1 +0 -20
  48. data/lib/gemstash/man/gemstash-version.1 +0 -22
@@ -1,227 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-private\-gems" "7" "October 8, 2015" "" ""
4
- .hy
5
- .SH PRIVATE GEMS
6
- .PP
7
- Stashing private gems in your Gemstash server requires a bit of
8
- additional setup.
9
- If you haven\[cq]t read through the Quickstart
10
- Guide (../readme.md#quickstart-guide), you should do that first.
11
- By the end of this guide, you will be able to interact with your
12
- Gemstash server to store and retrieve your private gems.
13
- .SS AUTHORIZING
14
- .PP
15
- \f[B]IMPORTANT NOTE:\f[R] Do not use the actual key value in this
16
- document, otherwise your Gemstash server will be vulnerable to anyone
17
- who wants to try to use the key against your server.
18
- Instead of the key value here, use whatever key is generated from
19
- running the commands.
20
- .PP
21
- In order to push a gem to your Gemstash server, you need to first create
22
- an API key.
23
- Utilize the \f[C]gemstash authorize\f[R] command to create the API key:
24
- .IP
25
- .nf
26
- \f[C]
27
- $ gemstash authorize
28
- Your new key is: e374e237fdf5fa5718d2a21bd63dc911
29
- \f[R]
30
- .fi
31
- .PP
32
- This new key can \f[C]push\f[R], \f[C]yank\f[R], and \f[C]fetch\f[R]
33
- gems from your Gemstash server.
34
- Run \f[C]gemstash authorize\f[R] with just the permissions you want to
35
- limit what the key will be allowed to do.
36
- You can similarly update a specific key by providing it via the
37
- \f[C]\-\-key\f[R] option:
38
- .IP
39
- .nf
40
- \f[C]
41
- $ gemstash authorize push yank \-\-key e374e237fdf5fa5718d2a21bd63dc911
42
- \f[R]
43
- .fi
44
- .PP
45
- When no permissions are provided (like the first example), the key will
46
- be authorized for all permissions.
47
- Leave the key authorized with everything if you want to use it to try
48
- all private gem interactions:
49
- .IP
50
- .nf
51
- \f[C]
52
- $ gemstash authorize \-\-key e374e237fdf5fa5718d2a21bd63dc911
53
- \f[R]
54
- .fi
55
- .PP
56
- With the key generated, you\[cq]ll need to tell Rubygems about your new
57
- key.
58
- If you\[cq]ve pushed a gem to https://rubygems.org, then you will
59
- already have a credentials file to add the key to.
60
- If not, run the following commands before modifying the credentials
61
- file:
62
- .IP
63
- .nf
64
- \f[C]
65
- $ mkdir \-p \[ti]/.gem
66
- $ touch \[ti]/.gem/credentials
67
- $ chmod 0600 \[ti]/.gem/credentials
68
- \f[R]
69
- .fi
70
- .PP
71
- Add your new key to credentials such that it looks something like this
72
- (but make sure not to remove any existing keys):
73
- .IP
74
- .nf
75
- \f[C]
76
- # \[ti]/.gem/credentials
77
- \-\-\-
78
- :test_key: e374e237fdf5fa5718d2a21bd63dc911
79
- \f[R]
80
- .fi
81
- .PP
82
- The name \f[C]test_key\f[R] can be anything you want, but you will need
83
- to remember it and use it again later in this guide for the
84
- \f[C]\-\-key\f[R] option.
85
- .SS CREATING A TEST GEM
86
- .PP
87
- You\[cq]ll need a test gem before you can play with private gems on your
88
- Gemstash server.
89
- If you have a gem you can use, move along to the next section.
90
- You can start by instantiating a test gem via Bundler:
91
- .IP
92
- .nf
93
- \f[C]
94
- $ bundle gem private\-example
95
- \f[R]
96
- .fi
97
- .PP
98
- You\[cq]ll need to add a summary and description to the new gem\[cq]s
99
- gemspec file in order to successfully build it.
100
- Once you\[cq]ve built the gem, you will be ready to push the new gem.
101
- .IP
102
- .nf
103
- \f[C]
104
- $ cd private\-example
105
- $ rake build
106
- \f[R]
107
- .fi
108
- .PP
109
- You will now have a gem at
110
- \f[C]private\-example/pkg/private\-example\-0.1.0.gem\f[R].
111
- .SS PUSHING
112
- .PP
113
- If your Gemstash server isn\[cq]t running, go ahead and start it:
114
- .IP
115
- .nf
116
- \f[C]
117
- $ gemstash start
118
- \f[R]
119
- .fi
120
- .PP
121
- Push your test gem using Rubygems:
122
- .IP
123
- .nf
124
- \f[C]
125
- $ gem push \-\-key test_key \-\-host http://localhost:9292/private pkg/private\-example\-0.1.0.gem
126
- \f[R]
127
- .fi
128
- .PP
129
- The \f[C]/private\f[R] portion of the \f[C]\-\-host\f[R] option tells
130
- Gemstash you are interacting with the private gems.
131
- Gemstash will not let you push, or yank from anything except
132
- \f[C]/private\f[R].
133
- .SS BUNDLING
134
- .PP
135
- Once your gem is pushed to your Gemstash server, you are ready to bundle
136
- it.
137
- Create a \f[C]Gemfile\f[R] and specify the gem.
138
- You will probably want to wrap the private gem in a source block, and
139
- let the rest of Gemstash handle all other gems:
140
- .IP
141
- .nf
142
- \f[C]
143
- # ./Gemfile
144
- source \[dq]http://localhost:9292\[dq]
145
- gem \[dq]rubywarrior\[dq]
146
-
147
- source \[dq]http://localhost:9292/private\[dq] do
148
- gem \[dq]private\-example\[dq]
149
- end
150
- \f[R]
151
- .fi
152
- .PP
153
- Notice that the Gemstash server points to \f[C]/private\f[R] again when
154
- installing your private gem.
155
- Go ahead and bundle to install your new private gem:
156
- .IP
157
- .nf
158
- \f[C]
159
- $ bundle
160
- \f[R]
161
- .fi
162
- .SS YANKING
163
- .PP
164
- If you push a private gem by accident, you can yank the gem with
165
- Rubygems:
166
- .IP
167
- .nf
168
- \f[C]
169
- $ RUBYGEMS_HOST=http://localhost:9292/private gem yank \-\-key test_key private\-example \-\-version 0.1.0
170
- \f[R]
171
- .fi
172
- .PP
173
- Like with pushing, the \f[C]/private\f[R] portion of the host option
174
- tells Gemstash you are interacting with private gems.
175
- Gemstash will only let you yank from \f[C]/private\f[R].
176
- Unlike pushing, Rubygems doesn\[cq]t support \f[C]\-\-host\f[R] for yank
177
- (yet), so you need to specify the host via the \f[C]RUBYGEMS_HOST\f[R]
178
- environment variable.
179
- .SS PROTECTED FETCHING
180
- .PP
181
- By default, private gems and specs can be accessed without
182
- authentication.
183
- .PP
184
- Private gems often require protected fetching.
185
- For backwards compatibility this is disabled by default, but can be
186
- enabled via \f[C]$ gemstash setup\f[R] command.
187
- .PP
188
- When protected fetching is enabled API keys with the permissions
189
- \f[C]all\f[R] or \f[C]fetch\f[R] can be used to download gems and specs.
190
- .PP
191
- On the Bundler side, there are a few ways to configure credentials for a
192
- given gem source:
193
- .PP
194
- Add credentials globally:
195
- .IP
196
- .nf
197
- \f[C]
198
- $ bundle config my\-gemstash.dev api_key
199
- \f[R]
200
- .fi
201
- .PP
202
- Add credentials in Gemfile:
203
- .IP
204
- .nf
205
- \f[C]
206
- source \[dq]https://api_key\[at]my\-gemstash.dev\[dq]
207
- \f[R]
208
- .fi
209
- .PP
210
- However, it\[cq]s not a good practice to commit credentials to source
211
- control.
212
- A recommended solution is to use Bundler\[cq]s configuration
213
- keys (http://bundler.io/man/bundle-config.1.html#CONFIGURATION-KEYS),
214
- e.g.:
215
- .IP
216
- .nf
217
- \f[C]
218
- $ export BUNDLE_MYGEMSTASH__DEV=api_key
219
- \f[R]
220
- .fi
221
- .PP
222
- Behind the scene, Bundler will pick up the ENV var according to the host
223
- name (e.g.\ mygemstash.dev) and add to \f[C]URI.userinfo\f[R] for making
224
- requests.
225
- .PP
226
- The API key is treated as a HTTP Basic Auth username and any HTTP Basic
227
- password supplied will be ignored.
@@ -1,233 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-readme" "7" "November 30, 2015" "" ""
4
- .hy
5
- .SH GEMSTASH
6
- .SS WHAT IS GEMSTASH?
7
- .PP
8
- Gemstash is both a cache for remote servers such as
9
- https://rubygems.org, and a private gem source.
10
- .PP
11
- If you are using bundler (http://bundler.io/) across many machines that
12
- have access to a server within your control, you might want to use
13
- Gemstash.
14
- .PP
15
- If you produce gems that you don\[cq]t want everyone in the world to
16
- have access to, you might want to use Gemstash.
17
- .PP
18
- If you frequently bundle the same set of gems across multiple projects,
19
- you might want to use Gemstash.
20
- .PP
21
- Are you only using gems from https://rubygems.org, and don\[cq]t bundle
22
- the same gems frequently?
23
- Well, maybe you don\[cq]t need Gemstash\&... yet.
24
- .PP
25
- Gemstash is maintained by Ruby Together (https://rubytogether.org/), a
26
- grassroots initiative committed to supporting the critical Ruby
27
- infrastructure you rely on.
28
- Contribute today as an individual (https://rubytogether.org/developers)
29
- or even better, as a company (https://rubytogether.org/companies), and
30
- ensure that Bundler, RubyGems, Gemstash, and other shared tooling is
31
- around for years to come.
32
- .SS QUICKSTART GUIDE
33
- .SS SETUP
34
- .PP
35
- Gemstash is designed to be quick and painless to get set up.
36
- By the end of this Quickstart Guide, you will be able to bundle stashed
37
- gems from public sources against a Gemstash server running on your
38
- machine.
39
- .PP
40
- Install Gemstash to get started:
41
- .IP
42
- .nf
43
- \f[C]
44
- $ gem install gemstash
45
- \f[R]
46
- .fi
47
- .PP
48
- After it is installed, starting Gemstash requires no additional steps.
49
- Simply start the Gemstash server with the \f[C]gemstash\f[R] command:
50
- .IP
51
- .nf
52
- \f[C]
53
- $ gemstash start
54
- \f[R]
55
- .fi
56
- .PP
57
- You may have noticed that the command finished quickly.
58
- This is because Gemstash will run the server in the background by
59
- default.
60
- The server runs on port 9292.
61
- .SS BUNDLING
62
- .PP
63
- With the server running, you can bundle against it.
64
- Tell Bundler that you want to use Gemstash to find gems from
65
- RubyGems.org:
66
- .IP
67
- .nf
68
- \f[C]
69
- $ bundle config mirror.https://rubygems.org http://localhost:9292
70
- \f[R]
71
- .fi
72
- .PP
73
- Now you can create a Gemfile and install gems through Gemstash:
74
- .IP
75
- .nf
76
- \f[C]
77
- # ./Gemfile
78
- source \[dq]https://rubygems.org\[dq]
79
- gem \[dq]rubywarrior\[dq]
80
- \f[R]
81
- .fi
82
- .PP
83
- The gems you include should be gems you don\[cq]t yet have installed,
84
- otherwise Gemstash will have nothing to stash.
85
- Now bundle:
86
- .IP
87
- .nf
88
- \f[C]
89
- $ bundle install \-\-path .bundle
90
- \f[R]
91
- .fi
92
- .PP
93
- Your Gemstash server has fetched the gems from https://rubygems.org and
94
- cached them for you! To prove this, you can disable your Internet
95
- connection and try again.
96
- Gem files (*.gem) are cached indefinitely.
97
- Gem dependencies metadata are cached for 30 minutes, so if you bundle
98
- again before that, you can successfully bundle without an Internet
99
- connection:
100
- .IP
101
- .nf
102
- \f[C]
103
- $ # Disable your Internet first!
104
- $ rm \-rf Gemfile.lock .bundle
105
- $ bundle
106
- \f[R]
107
- .fi
108
- .SS FALLING BACK TO RUBYGEMS.ORG
109
- .PP
110
- If you want to make sure that your bundling from https://rubygems.org
111
- still works as expected when the Gemstash server is not running, you can
112
- easily configure Bundler to fallback to https://rubygems.org.
113
- .IP
114
- .nf
115
- \f[C]
116
- $ bundle config mirror.https://rubygems.org.fallback_timeout true
117
- \f[R]
118
- .fi
119
- .PP
120
- You can also configure this fallback as a number of seconds in case the
121
- Gemstash server is simply unresponsive.
122
- This example uses a 3 second timeout:
123
- .IP
124
- .nf
125
- \f[C]
126
- $ bundle config mirror.https://rubygems.org.fallback_timeout 3
127
- \f[R]
128
- .fi
129
- .SS STOPPING THE SERVER
130
- .PP
131
- Once you\[cq]ve finish using your Gemstash server, you can stop it just
132
- as easily as you started it:
133
- .IP
134
- .nf
135
- \f[C]
136
- $ gemstash stop
137
- \f[R]
138
- .fi
139
- .PP
140
- You\[cq]ll also want to tell Bundler that it can go back to getting gems
141
- from RubyGems.org directly, instead of going through Gemstash:
142
- .IP
143
- .nf
144
- \f[C]
145
- $ bundle config \-\-delete mirror.https://rubygems.org
146
- \f[R]
147
- .fi
148
- .SS UNDER THE HOOD
149
- .PP
150
- You might wonder where the gems are stored.
151
- After running the commands above, you will find a new directory at
152
- \f[C]\[ti]/.gemstash\f[R].
153
- This directory holds all the cached and private gems.
154
- It also has a server log, the database, and configuration for Gemstash.
155
- If you prefer, you can point to a different
156
- directory (gemstash help customize.7).
157
- .PP
158
- Gemstash uses SQLite (https://www.sqlite.org/) to store details about
159
- private gems.
160
- The database will be located in \f[C]\[ti]/.gemstash\f[R], however you
161
- won\[cq]t see the database appear until you start using private gems.
162
- If you prefer, you can use a different
163
- database (gemstash help customize.7).
164
- .PP
165
- Gemstash temporarily caches things like gem dependencies in memory.
166
- Anything cached in memory will last for 30 minutes before being
167
- retrieved again.
168
- You can use memcached (gemstash help customize.7) instead of caching in
169
- memory.
170
- Gem files are always cached permanently, so bundling with a
171
- \f[C]Gemfile.lock\f[R] with all gems cached will never call out to
172
- https://rubygems.org.
173
- .PP
174
- The server you ran is provided via Puma (http://puma.io/) and
175
- Rack (http://rack.github.io/), however they are not customizable at this
176
- point.
177
- .SS DEEP DIVE
178
- .PP
179
- Deep dive into more subjects:
180
- .IP \[bu] 2
181
- Private gems (gemstash help private-gems.7)
182
- .IP \[bu] 2
183
- Multiple gem sources (gemstash help multiple-sources.7)
184
- .IP \[bu] 2
185
- Using Gemstash as a mirror (gemstash help mirror.7)
186
- .IP \[bu] 2
187
- Customizing the server (database, storage, caching, and
188
- more) (gemstash help customize.7)
189
- .IP \[bu] 2
190
- Deploying Gemstash (gemstash help deploy.7)
191
- .IP \[bu] 2
192
- Debugging Gemstash (gemstash help debugging.7)
193
- .SS REFERENCE
194
- .PP
195
- An anatomy of various configuration and commands:
196
- .IP \[bu] 2
197
- Configuration (gemstash help configuration.5)
198
- .IP \[bu] 2
199
- Authorize (gemstash help authorize.1)
200
- .IP \[bu] 2
201
- Start (gemstash help start.1)
202
- .IP \[bu] 2
203
- Stop (gemstash help stop.1)
204
- .IP \[bu] 2
205
- Status (gemstash help status.1)
206
- .IP \[bu] 2
207
- Setup (gemstash help setup.1)
208
- .IP \[bu] 2
209
- Version (gemstash help version.1)
210
- .PP
211
- To see what has changed in recent versions of Gemstash, see the
212
- CHANGELOG (https://github.com/rubygems/gemstash/blob/master/CHANGELOG.md).
213
- .SS DEVELOPMENT
214
- .PP
215
- After checking out the repo, run \f[C]bin/setup\f[R] to install
216
- dependencies.
217
- Then, run \f[C]rake\f[R] to run RuboCop and the tests.
218
- While developing, you can run \f[C]bin/gemstash\f[R] to run Gemstash.
219
- You can also run \f[C]bin/console\f[R] for an interactive prompt that
220
- will allow you to experiment.
221
- .SS CONTRIBUTING
222
- .PP
223
- Bug reports and pull requests are welcome on GitHub at
224
- https://github.com/rubygems/gemstash.
225
- This project is intended to be a safe, welcoming space for
226
- collaboration, and contributors are expected to adhere to the
227
- Contributor
228
- Covenant (https://github.com/rubygems/gemstash/blob/master/CODE_OF_CONDUCT.md)
229
- code of conduct.
230
- .SS LICENSE
231
- .PP
232
- The gem is available as open source under the terms of the MIT
233
- License (http://opensource.org/licenses/MIT).
@@ -1,43 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-setup" "1" "October 9, 2015" "" ""
4
- .hy
5
- .SH NAME
6
- .PP
7
- gemstash\-setup \- Customize your Gemstash configuration interactively
8
- .SH SYNOPSIS
9
- .PP
10
- \f[C]gemstash setup [\-\-redo] [\-\-debug] [\-\-config\-file FILE]\f[R]
11
- .SH DESCRIPTION
12
- .PP
13
- Customize your Gemstash configuration interactively.
14
- This will save your config file, but only if a few checks pass after
15
- you\[cq]ve provided your answers.
16
- .SS USAGE
17
- .IP
18
- .nf
19
- \f[C]
20
- gemstash setup
21
- gemstash setup \-\-redo
22
- gemstash setup \-\-config\-file <file>
23
- \f[R]
24
- .fi
25
- .SH OPTIONS
26
- .IP \[bu] 2
27
- \f[C]\-\-redo\f[R]: Redo the configuration.
28
- This does nothing the first time \f[C]gemstash setup\f[R] is run.
29
- If you want to change your configuration using \f[C]gemstash setup\f[R]
30
- after you\[cq]ve run it before, you must provide this option, otherwise
31
- Gemstash will simply indicate your setup is complete.
32
- .IP \[bu] 2
33
- \f[C]\-\-debug\f[R]: Output additional information if one of the checks
34
- at the end of setup fails.
35
- This will do nothing if all checks pass.
36
- .IP \[bu] 2
37
- \f[C]\-\-config\-file FILE\f[R]: Specify the config file to write to.
38
- Without this option, your configuration will be written to
39
- \f[C]\[ti]/.gemstash/config.yml\f[R].
40
- If you write to a custom location, you will need to pass the
41
- \f[C]\-\-config\-file\f[R] option to all Gemstash commands.
42
- If you plan to use ERB in your config file (gemstash help customize.7),
43
- you might want to use \f[C]\[ti]/.gemstash/config.yml.erb\f[R].
@@ -1,26 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-start" "1" "October 9, 2015" "" ""
4
- .hy
5
- .SH NAME
6
- .PP
7
- gemstash\-start \- Starts the Gemstash server
8
- .SH SYNOPSIS
9
- .PP
10
- \f[C]gemstash start [\-\-no\-daemonize] [\-\-config\-file FILE]\f[R]
11
- .SH DESCRIPTION
12
- .PP
13
- Starts the Gemstash server.
14
- .SH OPTIONS
15
- .IP \[bu] 2
16
- \f[C]\-\-config\-file FILE\f[R]: Specify the config file to use.
17
- If you aren\[cq]t using the default config file at
18
- \f[C]\[ti]/.gemstash/config.yml\f[R] or
19
- \f[C]\[ti]/.gemstash/config.yml.erb\f[R] (gemstash help customize.7),
20
- then you must specify the config file via this option.
21
- .IP \[bu] 2
22
- \f[C]\-\-no\-daemonize\f[R]: The Gemstash server daemonizes itself by
23
- default.
24
- Provide this option to instead run the server until \f[C]Ctrl\-C\f[R] is
25
- typed.
26
- When not daemonized, the log will be output to standard out.
@@ -1,20 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-status" "1" "October 28, 2015" "" ""
4
- .hy
5
- .SH NAME
6
- .PP
7
- gemstash\-status \- Checks status of the Gemstash server
8
- .SH SYNOPSIS
9
- .PP
10
- \f[C]gemstash status [\-\-config\-file FILE]\f[R]
11
- .SH DESCRIPTION
12
- .PP
13
- Checks status of the Gemstash server.
14
- .SH OPTIONS
15
- .IP \[bu] 2
16
- \f[C]\-\-config\-file FILE\f[R]: Specify the config file to use.
17
- If you aren\[cq]t using the default config file at
18
- \f[C]\[ti]/.gemstash/config.yml\f[R] or
19
- \f[C]\[ti]/.gemstash/config.yml.erb\f[R] (gemstash help customize.7),
20
- then you must specify the config file via this option.
@@ -1,20 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-stop" "1" "October 9, 2015" "" ""
4
- .hy
5
- .SH NAME
6
- .PP
7
- gemstash\-stop \- Stops the Gemstash server
8
- .SH SYNOPSIS
9
- .PP
10
- \f[C]gemstash stop [\-\-config\-file FILE]\f[R]
11
- .SH DESCRIPTION
12
- .PP
13
- Stops the Gemstash server.
14
- .SH OPTIONS
15
- .IP \[bu] 2
16
- \f[C]\-\-config\-file FILE\f[R]: Specify the config file to use.
17
- If you aren\[cq]t using the default config file at
18
- \f[C]\[ti]/.gemstash/config.yml\f[R] or
19
- \f[C]\[ti]/.gemstash/config.yml.erb\f[R] (gemstash help customize.7),
20
- then you must specify the config file via this option.
@@ -1,22 +0,0 @@
1
- .\" Automatically generated by Pandoc 2.5
2
- .\"
3
- .TH "gemstash\-version" "1" "December 14, 2015" "" ""
4
- .hy
5
- .SH NAME
6
- .PP
7
- gemstash\-version \- Show what version of Gemstash you are using
8
- .SH SYNOPSIS
9
- .PP
10
- \f[C]gemstash version\f[R]
11
- .SH DESCRIPTION
12
- .PP
13
- Show what version of Gemstash you are using.
14
- .SS USAGE
15
- .IP
16
- .nf
17
- \f[C]
18
- gemstash version
19
- gemstash \-\-version
20
- gemstash \-v
21
- \f[R]
22
- .fi