gemstash 2.2.0 → 2.2.1
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.
- checksums.yaml +4 -4
- data/lib/gemstash/cache.rb +1 -1
- data/lib/gemstash/man/gemstash-authorize.1 +66 -0
- data/lib/gemstash/man/gemstash-authorize.1.txt +47 -0
- data/lib/gemstash/man/gemstash-configuration.5 +241 -0
- data/lib/gemstash/man/gemstash-configuration.5.txt +211 -0
- data/lib/gemstash/man/gemstash-customize.7 +316 -0
- data/lib/gemstash/man/gemstash-customize.7.txt +187 -0
- data/lib/gemstash/man/gemstash-debugging.7 +49 -0
- data/lib/gemstash/man/gemstash-debugging.7.txt +30 -0
- data/lib/gemstash/man/gemstash-deploy.7 +87 -0
- data/lib/gemstash/man/gemstash-deploy.7.txt +60 -0
- data/lib/gemstash/man/gemstash-mirror.7 +55 -0
- data/lib/gemstash/man/gemstash-mirror.7.txt +34 -0
- data/lib/gemstash/man/gemstash-multiple-sources.7 +103 -0
- data/lib/gemstash/man/gemstash-multiple-sources.7.txt +71 -0
- data/lib/gemstash/man/gemstash-private-gems.7 +242 -0
- data/lib/gemstash/man/gemstash-private-gems.7.txt +157 -0
- data/lib/gemstash/man/gemstash-readme.7 +245 -0
- data/lib/gemstash/man/gemstash-readme.7.txt +181 -0
- data/lib/gemstash/man/gemstash-setup.1 +58 -0
- data/lib/gemstash/man/gemstash-setup.1.txt +41 -0
- data/lib/gemstash/man/gemstash-start.1 +41 -0
- data/lib/gemstash/man/gemstash-start.1.txt +27 -0
- data/lib/gemstash/man/gemstash-status.1 +35 -0
- data/lib/gemstash/man/gemstash-status.1.txt +23 -0
- data/lib/gemstash/man/gemstash-stop.1 +35 -0
- data/lib/gemstash/man/gemstash-stop.1.txt +23 -0
- data/lib/gemstash/man/gemstash-version.1 +37 -0
- data/lib/gemstash/man/gemstash-version.1.txt +22 -0
- data/lib/gemstash/version.rb +1 -1
- metadata +17 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: cb52dab0226e577b3119d1eccead8bcb09bd66226832824e53a8511860996c13
|
4
|
+
data.tar.gz: b13d821c0d1baa930c4107fd455be21b735c72f480a151d57640de20b134073a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 2b91f27500a36a8f8e412c992b026c4419f1bb63493f9325e8b1743ff28becba13648b16cbe93250e07ee4d42a1081c224928ba6269bdf4955c13259f47c82a7
|
7
|
+
data.tar.gz: 51bf8238974a3963719f38388d73a0ac1a480d5de67d3948df692a5823af56f70c632563db8c46e60ed28eaa70e4debb646aa8bc73bb2f291a19e07175619cfd
|
data/lib/gemstash/cache.rb
CHANGED
@@ -0,0 +1,66 @@
|
|
1
|
+
<!-- Automatically generated by Pandoc -->
|
2
|
+
.\" Automatically generated by Pandoc 3.0.1
|
3
|
+
.\"
|
4
|
+
.\" Define V font for inline verbatim, using C font in formats
|
5
|
+
.\" that render this, and otherwise B font.
|
6
|
+
.ie "\f[CB]x\f[]"x" \{\
|
7
|
+
. ftr V B
|
8
|
+
. ftr VI BI
|
9
|
+
. ftr VB B
|
10
|
+
. ftr VBI BI
|
11
|
+
.\}
|
12
|
+
.el \{\
|
13
|
+
. ftr V CR
|
14
|
+
. ftr VI CI
|
15
|
+
. ftr VB CB
|
16
|
+
. ftr VBI CBI
|
17
|
+
.\}
|
18
|
+
.TH "gemstash-authorize" "1" "October 9, 2015" "" ""
|
19
|
+
.hy
|
20
|
+
.SH Name
|
21
|
+
.PP
|
22
|
+
gemstash-authorize - Adds or removes authorization to interact with
|
23
|
+
privately stored gems
|
24
|
+
.SH Synopsis
|
25
|
+
.PP
|
26
|
+
\f[V]gemstash authorize [permissions] [--remove] [--key SECURE_KEY] [--config-file FILE]\f[R]
|
27
|
+
.SH Description
|
28
|
+
.PP
|
29
|
+
Adds or removes authorization to interact with privately stored gems.
|
30
|
+
.PP
|
31
|
+
Any arguments will be used as specific permissions.
|
32
|
+
Valid permissions include \f[V]push\f[R], \f[V]yank\f[R], and
|
33
|
+
\f[V]fetch\f[R].
|
34
|
+
If no permissions are provided, then all permissions will be granted
|
35
|
+
(including any that may be added in future versions of Gemstash).
|
36
|
+
.SS Usage
|
37
|
+
.IP
|
38
|
+
.nf
|
39
|
+
\f[C]
|
40
|
+
gemstash authorize
|
41
|
+
gemstash authorize push yank
|
42
|
+
gemstash authorize yank --key <secure-key>
|
43
|
+
gemstash authorize --remove --key <secure-key>
|
44
|
+
\f[R]
|
45
|
+
.fi
|
46
|
+
.SH Options
|
47
|
+
.IP \[bu] 2
|
48
|
+
\f[V]--config-file FILE\f[R]: Specify the config file to use.
|
49
|
+
If you aren\[cq]t using the default config file at
|
50
|
+
\f[V]\[ti]/.gemstash/config.yml\f[R] or
|
51
|
+
\f[V]\[ti]/.gemstash/config.yml.erb\f[R], then you must specify the
|
52
|
+
config file via this option.
|
53
|
+
.IP \[bu] 2
|
54
|
+
\f[V]--key SECURE_KEY\f[R]: Specify the API key to affect.
|
55
|
+
This should be the actual key value, not a name.
|
56
|
+
This option is required when using \f[V]--remove\f[R] but is optional
|
57
|
+
otherwise.
|
58
|
+
If adding an authorization, using this will either create or update the
|
59
|
+
permissions for the specified API key.
|
60
|
+
If missing, a new API key will always be generated.
|
61
|
+
Note that a key can only have a maximum length of 255 chars.
|
62
|
+
.IP \[bu] 2
|
63
|
+
\f[V]--remove\f[R]: Remove an authorization rather than add or update
|
64
|
+
one.
|
65
|
+
When removing, permission values are not allowed.
|
66
|
+
The \f[V]--key <secure-key>\f[R] option is required.
|
@@ -1 +1,48 @@
|
|
1
|
+
gemstash-authorize(1) gemstash-authorize(1)
|
1
2
|
|
3
|
+
|
4
|
+
|
5
|
+
<!-- Automatically generated by Pandoc -->
|
6
|
+
|
7
|
+
1mName0m
|
8
|
+
gemstash-authorize - Adds or removes authorization to interact with
|
9
|
+
privately stored gems
|
10
|
+
|
11
|
+
1mSynopsis0m
|
12
|
+
1mgemstash authorize [permissions] [--remove] [--key SECURE_KEY] [--con-0m
|
13
|
+
1mfig-file FILE]0m
|
14
|
+
|
15
|
+
1mDescription0m
|
16
|
+
Adds or removes authorization to interact with privately stored gems.
|
17
|
+
|
18
|
+
Any arguments will be used as specific permissions. Valid permissions
|
19
|
+
include 1mpush22m, 1myank22m, and 1mfetch22m. If no permissions are provided, then
|
20
|
+
all permissions will be granted (including any that may be added in fu-
|
21
|
+
ture versions of Gemstash).
|
22
|
+
|
23
|
+
1mUsage0m
|
24
|
+
gemstash authorize
|
25
|
+
gemstash authorize push yank
|
26
|
+
gemstash authorize yank --key <secure-key>
|
27
|
+
gemstash authorize --remove --key <secure-key>
|
28
|
+
|
29
|
+
1mOptions0m
|
30
|
+
o 1m--config-file FILE22m: Specify the config file to use. If you aren't
|
31
|
+
using the default config file at 1m~/.gemstash/config.yml 22mor 1m~/.gem-0m
|
32
|
+
1mstash/config.yml.erb22m, then you must specify the config file via this
|
33
|
+
option.
|
34
|
+
|
35
|
+
o 1m--key SECURE_KEY22m: Specify the API key to affect. This should be the
|
36
|
+
actual key value, not a name. This option is required when using
|
37
|
+
1m--remove 22mbut is optional otherwise. If adding an authorization, us-
|
38
|
+
ing this will either create or update the permissions for the speci-
|
39
|
+
fied API key. If missing, a new API key will always be generated.
|
40
|
+
Note that a key can only have a maximum length of 255 chars.
|
41
|
+
|
42
|
+
o 1m--remove22m: Remove an authorization rather than add or update one.
|
43
|
+
When removing, permission values are not allowed. The 1m--key <secure-0m
|
44
|
+
1mkey> 22moption is required.
|
45
|
+
|
46
|
+
|
47
|
+
|
48
|
+
October 9, 2015 gemstash-authorize(1)
|
@@ -0,0 +1,241 @@
|
|
1
|
+
<!-- Automatically generated by Pandoc -->
|
2
|
+
.\" Automatically generated by Pandoc 3.0.1
|
3
|
+
.\"
|
4
|
+
.\" Define V font for inline verbatim, using C font in formats
|
5
|
+
.\" that render this, and otherwise B font.
|
6
|
+
.ie "\f[CB]x\f[]"x" \{\
|
7
|
+
. ftr V B
|
8
|
+
. ftr VI BI
|
9
|
+
. ftr VB B
|
10
|
+
. ftr VBI BI
|
11
|
+
.\}
|
12
|
+
.el \{\
|
13
|
+
. ftr V CR
|
14
|
+
. ftr VI CI
|
15
|
+
. ftr VB CB
|
16
|
+
. ftr VBI CBI
|
17
|
+
.\}
|
18
|
+
.TH "gemstash-configuration" "5" "October 13, 2015" "" ""
|
19
|
+
.hy
|
20
|
+
.SH Name
|
21
|
+
.PP
|
22
|
+
gemstash-configuration
|
23
|
+
.SH Synopsis
|
24
|
+
.IP
|
25
|
+
.nf
|
26
|
+
\f[C]
|
27
|
+
# \[ti]/.gemstash/config.yml
|
28
|
+
---
|
29
|
+
:base_path: \[dq]/var/gemstash\[dq]
|
30
|
+
:cache_type: memcached
|
31
|
+
:memcached_servers: localhost:11211
|
32
|
+
:db_adapter: postgres
|
33
|
+
:db_url: postgres:///gemstash
|
34
|
+
:db_connection_options:
|
35
|
+
:test: true
|
36
|
+
:pool_timeout: 2
|
37
|
+
:rubygems_url: https://my.gem-source.local
|
38
|
+
:ignore_gemfile_source: false
|
39
|
+
:puma_threads: 32
|
40
|
+
:bind: tcp://0.0.0.0:4242
|
41
|
+
:protected_fetch: true
|
42
|
+
:fetch_timeout: 10
|
43
|
+
:log_file: gemstash.log
|
44
|
+
\f[R]
|
45
|
+
.fi
|
46
|
+
.SH Base Path
|
47
|
+
.PP
|
48
|
+
\f[V]:base_path\f[R]
|
49
|
+
.PP
|
50
|
+
Specifies where to store local files like the server log, cached gem
|
51
|
+
files, and the database (when using SQLite).
|
52
|
+
If the default is being used, the directory will be created if it does
|
53
|
+
not exist.
|
54
|
+
Any other directory needs to be created ahead of time and be writable to
|
55
|
+
the Gemstash server process.
|
56
|
+
Specifying the \f[V]:base_path\f[R] via \f[V]gemstash setup\f[R] will
|
57
|
+
create the directory for you.
|
58
|
+
.SS Default value
|
59
|
+
.PP
|
60
|
+
\f[V]\[ti]/.gemstash\f[R]
|
61
|
+
.SS Valid values
|
62
|
+
.PP
|
63
|
+
Any valid path
|
64
|
+
.SH Cache Type
|
65
|
+
.PP
|
66
|
+
\f[V]:cache_type\f[R]
|
67
|
+
.PP
|
68
|
+
Specifies how to cache values other than gem files (such as gem
|
69
|
+
dependencies).
|
70
|
+
\f[V]memory\f[R] will use an in memory cache while \f[V]memcached\f[R]
|
71
|
+
will point to 1 or more Memcached servers.
|
72
|
+
Use the \f[V]:memcached_servers\f[R] configuration key for specifying
|
73
|
+
where the Memcached server(s) are.
|
74
|
+
.SS Default value
|
75
|
+
.PP
|
76
|
+
\f[V]memory\f[R]
|
77
|
+
.SS Valid values
|
78
|
+
.PP
|
79
|
+
\f[V]memory\f[R], \f[V]memcached\f[R]
|
80
|
+
.SH Memcached Servers
|
81
|
+
.PP
|
82
|
+
\f[V]:memcached_servers\f[R]
|
83
|
+
.PP
|
84
|
+
Specifies the Memcached servers to connect to when using
|
85
|
+
\f[V]memcached\f[R] for the \f[V]:cache_type\f[R].
|
86
|
+
Only used when \f[V]memcached\f[R] is used for \f[V]:cache_type\f[R].
|
87
|
+
.SS Default value
|
88
|
+
.PP
|
89
|
+
\f[V]localhost:11211\f[R]
|
90
|
+
.SS Valid values
|
91
|
+
.PP
|
92
|
+
A comma delimited list of Memcached servers
|
93
|
+
.SH DB Adapter
|
94
|
+
.PP
|
95
|
+
\f[V]:db_adapter\f[R]
|
96
|
+
.PP
|
97
|
+
Specifies what database adapter to use.
|
98
|
+
When \f[V]sqlite3\f[R] is used, the database will be located at
|
99
|
+
\f[V]gemstash.db\f[R] within the directory specified by
|
100
|
+
\f[V]:base_path\f[R].
|
101
|
+
The database will automatically be created when using \f[V]sqlite3\f[R].
|
102
|
+
When \f[V]postgres\f[R], \f[V]mysql\f[R], or \f[V]mysql2\f[R] is used,
|
103
|
+
the database to connect to must be specified in the \f[V]:db_url\f[R]
|
104
|
+
configuration key.
|
105
|
+
The database must already be created when using anything other than
|
106
|
+
\f[V]sqlite3\f[R].
|
107
|
+
.SS Default value
|
108
|
+
.PP
|
109
|
+
\f[V]sqlite3\f[R]
|
110
|
+
.SS Valid values
|
111
|
+
.PP
|
112
|
+
\f[V]sqlite3\f[R], \f[V]postgres\f[R], \f[V]mysql\f[R], \f[V]mysql2\f[R]
|
113
|
+
.SH DB URL
|
114
|
+
.PP
|
115
|
+
\f[V]:db_url\f[R]
|
116
|
+
.PP
|
117
|
+
Specifies the database to connect to when using \f[V]postgres\f[R],
|
118
|
+
\f[V]mysql\f[R], or \f[V]mysql2\f[R] for the \f[V]:db_adapter\f[R].
|
119
|
+
Only used when the \f[V]:db_adapter\f[R] is not \f[V]sqlite3\f[R].
|
120
|
+
.SS Default value
|
121
|
+
.PP
|
122
|
+
None
|
123
|
+
.SS Valid values
|
124
|
+
.PP
|
125
|
+
A valid database URL for the Sequel gem (http://sequel.jeremyevans.net/)
|
126
|
+
.SH DB Connection Options
|
127
|
+
.PP
|
128
|
+
\f[V]:db_connection_options\f[R]
|
129
|
+
.PP
|
130
|
+
Specifies additional \f[V]Sequel.connect\f[R] options to use.
|
131
|
+
Note that any options here are merged in with the default options, so
|
132
|
+
you need not specify the \f[V]max_connections\f[R] if you customize this
|
133
|
+
option.
|
134
|
+
.SS Default value
|
135
|
+
.PP
|
136
|
+
\f[V]{ max_connections: 1 }\f[R] for \f[V]sqlite3\f[R] adapter,
|
137
|
+
\f[V]{ max_connections: config[:puma_threads] + 1 }\f[R] for any other
|
138
|
+
adapter.
|
139
|
+
.SS Valid values
|
140
|
+
.PP
|
141
|
+
A valid connection options Hash for the
|
142
|
+
Sequel.connect (http://sequel.jeremyevans.net/rdoc/files/doc/opening_databases_rdoc.html#label-General+connection+options)
|
143
|
+
method.
|
144
|
+
.SH Rubygems URL
|
145
|
+
.PP
|
146
|
+
\f[V]:rubygems_url\f[R]
|
147
|
+
.PP
|
148
|
+
Specifies the default gem source URL.
|
149
|
+
When any API endpoint is called without a \f[V]/private\f[R] or
|
150
|
+
\f[V]/upstream/<url>\f[R] prefix, this URL will be used to fetch the
|
151
|
+
result.
|
152
|
+
This value can be safely changed even if there are already gems stashed
|
153
|
+
for the previous value.
|
154
|
+
.SS Default value
|
155
|
+
.PP
|
156
|
+
\f[V]https://rubygems.org\f[R]
|
157
|
+
.SS Valid values
|
158
|
+
.PP
|
159
|
+
A valid gem source URL
|
160
|
+
.SH Ignore Gemfile source
|
161
|
+
.PP
|
162
|
+
\f[V]:ignore_gemfile_source\f[R]
|
163
|
+
.PP
|
164
|
+
Ignore the source specified in Gemfile and always use
|
165
|
+
\f[V]:rubygems_url\f[R] as gems upstream.
|
166
|
+
.SS Default value
|
167
|
+
.PP
|
168
|
+
\f[V]false\f[R]
|
169
|
+
.SS Valid values
|
170
|
+
.PP
|
171
|
+
Boolean: \f[V]true\f[R] or \f[V]false\f[R]
|
172
|
+
.SH Puma Threads
|
173
|
+
.PP
|
174
|
+
\f[V]:puma_threads\f[R]
|
175
|
+
.PP
|
176
|
+
Specifies the number of threads used for the Gemstash server.
|
177
|
+
.SS Default value
|
178
|
+
.PP
|
179
|
+
\f[V]16\f[R]
|
180
|
+
.SS Valid values
|
181
|
+
.PP
|
182
|
+
Integer value with a minimum of \f[V]1\f[R]
|
183
|
+
.SH Bind Address
|
184
|
+
.PP
|
185
|
+
\f[V]:bind\f[R]
|
186
|
+
.PP
|
187
|
+
Specifies the binding used to start the Gemstash server.
|
188
|
+
Keep in mind the user starting Gemstash needs to have access to bind in
|
189
|
+
this manner.
|
190
|
+
For example, if you use a port below 1024, you will need to run Gemstash
|
191
|
+
as the root user.
|
192
|
+
.SS Default value
|
193
|
+
.PP
|
194
|
+
\f[V]tcp://0.0.0.0:9292\f[R]
|
195
|
+
.SS Valid values
|
196
|
+
.PP
|
197
|
+
Any valid binding that is supported by
|
198
|
+
Puma (https://github.com/puma/puma#binding-tcp--sockets)
|
199
|
+
.SH Protected Fetch
|
200
|
+
.PP
|
201
|
+
\f[V]:protected_fetch\f[R]
|
202
|
+
.PP
|
203
|
+
Tells Gemstash to authenticate via an API key before allowing the
|
204
|
+
fetching of private gems and specs.
|
205
|
+
The default behavior is to allow unauthenticated download of private
|
206
|
+
gems and specs.
|
207
|
+
.SS Default value
|
208
|
+
.PP
|
209
|
+
\f[V]false\f[R]
|
210
|
+
.SS Valid values
|
211
|
+
.PP
|
212
|
+
Boolean values \f[V]true\f[R] or \f[V]false\f[R]
|
213
|
+
.SH Fetch Timeout
|
214
|
+
.PP
|
215
|
+
\f[V]:fetch_timeout\f[R]
|
216
|
+
.PP
|
217
|
+
The timeout setting for fetching gems.
|
218
|
+
Fetching gems over a slow connection may cause timeout errors.
|
219
|
+
If you experience timeout errors, you may want to increase this value.
|
220
|
+
The default is \f[V]20\f[R] seconds.
|
221
|
+
.SS Default value
|
222
|
+
.PP
|
223
|
+
\f[V]20\f[R]
|
224
|
+
.SS Valid values
|
225
|
+
.PP
|
226
|
+
Integer value with a minimum of \f[V]1\f[R]
|
227
|
+
.SH Log File
|
228
|
+
.PP
|
229
|
+
\f[V]:log_file\f[R]
|
230
|
+
.PP
|
231
|
+
Indicates the name of the file to use for logging.
|
232
|
+
The file will be placed in the base path.
|
233
|
+
.SS Default value
|
234
|
+
.PP
|
235
|
+
\f[V]server.log\f[R]
|
236
|
+
.SS Valid values
|
237
|
+
.PP
|
238
|
+
Any valid file name, or \f[V]:stdout\f[R] to log to \f[V]$stdout\f[R]
|
239
|
+
.PP
|
240
|
+
\f[I]Note: Using \f[VI]:stdout\f[I] for the \f[VI]:log_file\f[I]
|
241
|
+
requires running with \f[VI]--no-daemonize\f[I].\f[R]
|
@@ -1 +1,212 @@
|
|
1
|
+
gemstash-configuration(5) gemstash-configuration(5)
|
1
2
|
|
3
|
+
|
4
|
+
|
5
|
+
<!-- Automatically generated by Pandoc -->
|
6
|
+
|
7
|
+
1mName0m
|
8
|
+
gemstash-configuration
|
9
|
+
|
10
|
+
1mSynopsis0m
|
11
|
+
# ~/.gemstash/config.yml
|
12
|
+
---
|
13
|
+
:base_path: "/var/gemstash"
|
14
|
+
:cache_type: memcached
|
15
|
+
:memcached_servers: localhost:11211
|
16
|
+
:db_adapter: postgres
|
17
|
+
:db_url: postgres:///gemstash
|
18
|
+
:db_connection_options:
|
19
|
+
:test: true
|
20
|
+
:pool_timeout: 2
|
21
|
+
:rubygems_url: https://my.gem-source.local
|
22
|
+
:ignore_gemfile_source: false
|
23
|
+
:puma_threads: 32
|
24
|
+
:bind: tcp://0.0.0.0:4242
|
25
|
+
:protected_fetch: true
|
26
|
+
:fetch_timeout: 10
|
27
|
+
:log_file: gemstash.log
|
28
|
+
|
29
|
+
1mBase Path0m
|
30
|
+
1m:base_path0m
|
31
|
+
|
32
|
+
Specifies where to store local files like the server log, cached gem
|
33
|
+
files, and the database (when using SQLite). If the default is being
|
34
|
+
used, the directory will be created if it does not exist. Any other
|
35
|
+
directory needs to be created ahead of time and be writable to the Gem-
|
36
|
+
stash server process. Specifying the 1m:base_path 22mvia 1mgemstash setup0m
|
37
|
+
will create the directory for you.
|
38
|
+
|
39
|
+
1mDefault value0m
|
40
|
+
1m~/.gemstash0m
|
41
|
+
|
42
|
+
1mValid values0m
|
43
|
+
Any valid path
|
44
|
+
|
45
|
+
1mCache Type0m
|
46
|
+
1m:cache_type0m
|
47
|
+
|
48
|
+
Specifies how to cache values other than gem files (such as gem depen-
|
49
|
+
dencies). 1mmemory 22mwill use an in memory cache while 1mmemcached 22mwill
|
50
|
+
point to 1 or more Memcached servers. Use the 1m:memcached_servers 22mcon-
|
51
|
+
figuration key for specifying where the Memcached server(s) are.
|
52
|
+
|
53
|
+
1mDefault value0m
|
54
|
+
1mmemory0m
|
55
|
+
|
56
|
+
1mValid values0m
|
57
|
+
1mmemory22m, 1mmemcached0m
|
58
|
+
|
59
|
+
1mMemcached Servers0m
|
60
|
+
1m:memcached_servers0m
|
61
|
+
|
62
|
+
Specifies the Memcached servers to connect to when using 1mmemcached 22mfor
|
63
|
+
the 1m:cache_type22m. Only used when 1mmemcached 22mis used for 1m:cache_type22m.
|
64
|
+
|
65
|
+
1mDefault value0m
|
66
|
+
1mlocalhost:112110m
|
67
|
+
|
68
|
+
1mValid values0m
|
69
|
+
A comma delimited list of Memcached servers
|
70
|
+
|
71
|
+
1mDB Adapter0m
|
72
|
+
1m:db_adapter0m
|
73
|
+
|
74
|
+
Specifies what database adapter to use. When 1msqlite3 22mis used, the
|
75
|
+
database will be located at 1mgemstash.db 22mwithin the directory specified
|
76
|
+
by 1m:base_path22m. The database will automatically be created when using
|
77
|
+
1msqlite322m. When 1mpostgres22m, 1mmysql22m, or 1mmysql2 22mis used, the database to con-
|
78
|
+
nect to must be specified in the 1m:db_url 22mconfiguration key. The data-
|
79
|
+
base must already be created when using anything other than 1msqlite322m.
|
80
|
+
|
81
|
+
1mDefault value0m
|
82
|
+
1msqlite30m
|
83
|
+
|
84
|
+
1mValid values0m
|
85
|
+
1msqlite322m, 1mpostgres22m, 1mmysql22m, 1mmysql20m
|
86
|
+
|
87
|
+
1mDB URL0m
|
88
|
+
1m:db_url0m
|
89
|
+
|
90
|
+
Specifies the database to connect to when using 1mpostgres22m, 1mmysql22m, or
|
91
|
+
1mmysql2 22mfor the 1m:db_adapter22m. Only used when the 1m:db_adapter 22mis not
|
92
|
+
1msqlite322m.
|
93
|
+
|
94
|
+
1mDefault value0m
|
95
|
+
None
|
96
|
+
|
97
|
+
1mValid values0m
|
98
|
+
A valid database URL for the Sequel gem (http://sequel.jeremye-
|
99
|
+
vans.net/)
|
100
|
+
|
101
|
+
1mDB Connection Options0m
|
102
|
+
1m:db_connection_options0m
|
103
|
+
|
104
|
+
Specifies additional 1mSequel.connect 22moptions to use. Note that any op-
|
105
|
+
tions here are merged in with the default options, so you need not
|
106
|
+
specify the 1mmax_connections 22mif you customize this option.
|
107
|
+
|
108
|
+
1mDefault value0m
|
109
|
+
1m{ max_connections: 1 } 22mfor 1msqlite3 22madapter, 1m{ max_connections: con-0m
|
110
|
+
1mfig[:puma_threads] + 1 } 22mfor any other adapter.
|
111
|
+
|
112
|
+
1mValid values0m
|
113
|
+
A valid connection options Hash for the Sequel.connect (http://se-
|
114
|
+
quel.jeremyevans.net/rdoc/files/doc/opening_databases_rdoc.html#label-
|
115
|
+
General+connection+options) method.
|
116
|
+
|
117
|
+
1mRubygems URL0m
|
118
|
+
1m:rubygems_url0m
|
119
|
+
|
120
|
+
Specifies the default gem source URL. When any API endpoint is called
|
121
|
+
without a 1m/private 22mor 1m/upstream/<url> 22mprefix, this URL will be used to
|
122
|
+
fetch the result. This value can be safely changed even if there are
|
123
|
+
already gems stashed for the previous value.
|
124
|
+
|
125
|
+
1mDefault value0m
|
126
|
+
1mhttps://rubygems.org0m
|
127
|
+
|
128
|
+
1mValid values0m
|
129
|
+
A valid gem source URL
|
130
|
+
|
131
|
+
1mIgnore Gemfile source0m
|
132
|
+
1m:ignore_gemfile_source0m
|
133
|
+
|
134
|
+
Ignore the source specified in Gemfile and always use 1m:rubygems_url 22mas
|
135
|
+
gems upstream.
|
136
|
+
|
137
|
+
1mDefault value0m
|
138
|
+
1mfalse0m
|
139
|
+
|
140
|
+
1mValid values0m
|
141
|
+
Boolean: 1mtrue 22mor 1mfalse0m
|
142
|
+
|
143
|
+
1mPuma Threads0m
|
144
|
+
1m:puma_threads0m
|
145
|
+
|
146
|
+
Specifies the number of threads used for the Gemstash server.
|
147
|
+
|
148
|
+
1mDefault value0m
|
149
|
+
1m160m
|
150
|
+
|
151
|
+
1mValid values0m
|
152
|
+
Integer value with a minimum of 1m10m
|
153
|
+
|
154
|
+
1mBind Address0m
|
155
|
+
1m:bind0m
|
156
|
+
|
157
|
+
Specifies the binding used to start the Gemstash server. Keep in mind
|
158
|
+
the user starting Gemstash needs to have access to bind in this manner.
|
159
|
+
For example, if you use a port below 1024, you will need to run Gem-
|
160
|
+
stash as the root user.
|
161
|
+
|
162
|
+
1mDefault value0m
|
163
|
+
1mtcp://0.0.0.0:92920m
|
164
|
+
|
165
|
+
1mValid values0m
|
166
|
+
Any valid binding that is supported by Puma
|
167
|
+
(https://github.com/puma/puma#binding-tcp--sockets)
|
168
|
+
|
169
|
+
1mProtected Fetch0m
|
170
|
+
1m:protected_fetch0m
|
171
|
+
|
172
|
+
Tells Gemstash to authenticate via an API key before allowing the
|
173
|
+
fetching of private gems and specs. The default behavior is to allow
|
174
|
+
unauthenticated download of private gems and specs.
|
175
|
+
|
176
|
+
1mDefault value0m
|
177
|
+
1mfalse0m
|
178
|
+
|
179
|
+
1mValid values0m
|
180
|
+
Boolean values 1mtrue 22mor 1mfalse0m
|
181
|
+
|
182
|
+
1mFetch Timeout0m
|
183
|
+
1m:fetch_timeout0m
|
184
|
+
|
185
|
+
The timeout setting for fetching gems. Fetching gems over a slow con-
|
186
|
+
nection may cause timeout errors. If you experience timeout errors,
|
187
|
+
you may want to increase this value. The default is 1m20 22mseconds.
|
188
|
+
|
189
|
+
1mDefault value0m
|
190
|
+
1m200m
|
191
|
+
|
192
|
+
1mValid values0m
|
193
|
+
Integer value with a minimum of 1m10m
|
194
|
+
|
195
|
+
1mLog File0m
|
196
|
+
1m:log_file0m
|
197
|
+
|
198
|
+
Indicates the name of the file to use for logging. The file will be
|
199
|
+
placed in the base path.
|
200
|
+
|
201
|
+
1mDefault value0m
|
202
|
+
1mserver.log0m
|
203
|
+
|
204
|
+
1mValid values0m
|
205
|
+
Any valid file name, or 1m:stdout 22mto log to 1m$stdout0m
|
206
|
+
|
207
|
+
4mNote:24m 4mUsing24m 4m1m:stdout24m 4m22mfor24m 4mthe24m 4m1m:log_file24m 4m22mrequires24m 4mrunning24m 4mwith24m 4m1m--no-daemo-0m
|
208
|
+
4m1mnize22m.0m
|
209
|
+
|
210
|
+
|
211
|
+
|
212
|
+
October 13, 2015 gemstash-configuration(5)
|