gemstash 2.3.2 → 2.4.0

data/lib/gemstash/man/gemstash-deploy.7.txt

@@ -4,16 +4,16 @@
 
 1mDeploying Gemstash0m
        Bundler	is  here for the rescue to keep Gemstash up to date!  Create a
-       1mGemfile 22mpointing to Gemstash:
+       Gemfile pointing to Gemstash:
 
 	      # ./Gemfile
 	      source "https://rubygems.org"
 	      gem "gemstash"
 
-       Then 1mbundle 22mto create your 1mGemfile.lock22m.  When you  are  ready  to  up-
-       grade,  simply  1mbundle update22m.  You may need to run 1mgemstash 22mvia 1mbundle0m
-       1mexec22m.  Alternatively, you can 1mgem uninstall gemstash  22mand  1mgem  install0m
-       1mgemstash 22mwhen you want to upgrade.
+       Then bundle to create your Gemfile.lock.  When you  are	ready  to  up-
+       grade,  simply  bundle update.  You may need to run gemstash via bundle
+       exec.  Alternatively, you can gem uninstall gemstash  and  gem  install
+       gemstash when you want to upgrade.
 
        Gemstash  will  automatically run any necessary migrations, so updating
        the gem is all that needs to be done.
@@ -26,12 +26,12 @@
 	      $ bundle exec gemstash start
 
    1mMonitoring0m
-       Health	monitoring   is   built   in   to  Gemstash  using  the  serv-
-       er_health_check-rack   (https://github.com/on-site/server_health_check-
-       rack)  gem.   If  you  request 1m/health 22mfrom your Gemstash instance, you
-       will get a JSON response along with an HTTP status code indicating suc-
-       cess or failure.  The JSON response will look something like this for a
-       success case:
+       Health	 monitoring    is    built    in   to	Gemstash   using   the
+       server_health_check-rack 		       (https://github.com/on-
+       site/server_health_check-rack)  gem.   If you request /health from your
+       Gemstash instance, you will get a JSON response along with an HTTP sta-
+       tus code indicating success or failure.	The JSON  response  will  look
+       something like this for a success case:
 
 	      {
 		"status": {
@@ -43,11 +43,11 @@
 		}
 	      }
 
-       This request will test storage and database access and  report  on  the
-       result.	 Each  key in the status can be requested alone to just report
-       on that status.	For example, if you would like	a  health  check  that
-       doesn't	 interact   with   storage   or  the  database,  you  can  use
-       1m/health/heartbeat 22mwhich will always respond with a success	while  your
+       This  request  will  test storage and database access and report on the
+       result.	Each key in the status can be requested alone to  just	report
+       on  that  status.   For	example, if you would like a health check that
+       doesn't	interact  with	storage  or  the   database,   you   can   use
+       /health/heartbeat  which  will always respond with a success while your
        Gemstash server is running.
 
    1mDowngrading0m

data/lib/gemstash/man/gemstash-mirror.7

@@ -1,55 +1,34 @@
 <!-- Automatically generated by Pandoc -->
-.\" Automatically generated by Pandoc 3.1.6.2
+.\" Automatically generated by Pandoc 3.1.8
 .\"
-.\" Define V font for inline verbatim, using C font in formats
-.\" that render this, and otherwise B font.
-.ie "\f[CB]x\f[]"x" \{\
-. ftr V B
-. ftr VI BI
-. ftr VB B
-. ftr VBI BI
-.\}
-.el \{\
-. ftr V CR
-. ftr VI CI
-. ftr VB CB
-. ftr VBI CBI
-.\}
 .TH "gemstash-mirror" "7" "October 25, 2015" "" ""
-.hy
 .SH Using Gemstash as a Mirror
-.PP
-If you don\[cq]t have control over your \f[V]Gemfile\f[R], or you
+If you don\[cq]t have control over your \f[CR]Gemfile\f[R], or you
 don\[cq]t want to force everyone on your team to go through the Gemstash
 server, you can use Bundler mirroring to bundle against your Gemstash
 server.
 .PP
-For each source in your \f[V]Gemfile\f[R], add a mirror pointing to your
-Gemstash server:
+For each source in your \f[CR]Gemfile\f[R], add a mirror pointing to
+your Gemstash server:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config mirror.http://rubygems.org http://localhost:9292
 $ bundle config mirror.https://my.gem-source.local http://localhost:9292/upstream/$(ruby -rcgi -e \[aq]puts CGI.escape(\[dq]https://my.gem-source.local\[dq])\[aq])
-\f[R]
-.fi
+.EE
 .PP
 From now on, bundler will fetch gems from those sources via your
 Gemstash server.
 .SH Simpler Gemstash Mirrors
-.PP
 \f[B]This feature requires Bundler to be at least version
-\f[VB]1.11.0\f[B].\f[R]
+\f[CB]1.11.0\f[B].\f[R]
 .PP
-If you are using Bundler version \f[V]1.11.0\f[R] or greater, the
+If you are using Bundler version \f[CR]1.11.0\f[R] or greater, the
 mirroring becomes a bit easier:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config mirror.http://rubygems.org http://localhost:9292
 $ bundle config mirror.https://my.gem-source.local http://localhost:9292
-\f[R]
-.fi
+.EE
 .PP
 Bundler will then send headers to Gemstash to indicate the correct
 upstream.

data/lib/gemstash/man/gemstash-mirror.7.txt

@@ -3,11 +3,11 @@
 <!-- Automatically generated by Pandoc -->
 
 1mUsing Gemstash as a Mirror0m
-       If you don't have control over your 1mGemfile22m, or you don't want to force
+       If you don't have control over your Gemfile, or you don't want to force
        everyone  on  your  team to go through the Gemstash server, you can use
        Bundler mirroring to bundle against your Gemstash server.
 
-       For each source in your 1mGemfile22m, add a mirror pointing to your Gemstash
+       For each source in your Gemfile, add a mirror pointing to your Gemstash
        server:
 
 	      $ bundle config mirror.http://rubygems.org http://localhost:9292
@@ -19,7 +19,7 @@
 1mSimpler Gemstash Mirrors0m
        1mThis feature requires Bundler to be at least version 1.11.0.0m
 
-       If  you	are using Bundler version 1m1.11.0 22mor greater, the mirroring be-
+       If  you	are using Bundler version 1.11.0 or greater, the mirroring be-
        comes a bit easier:
 
 	      $ bundle config mirror.http://rubygems.org http://localhost:9292

data/lib/gemstash/man/gemstash-multiple-sources.7

@@ -1,69 +1,46 @@
 <!-- Automatically generated by Pandoc -->
-.\" Automatically generated by Pandoc 3.1.6.2
+.\" Automatically generated by Pandoc 3.1.8
 .\"
-.\" Define V font for inline verbatim, using C font in formats
-.\" that render this, and otherwise B font.
-.ie "\f[CB]x\f[]"x" \{\
-. ftr V B
-. ftr VI BI
-. ftr VB B
-. ftr VBI BI
-.\}
-.el \{\
-. ftr V CR
-. ftr VI CI
-. ftr VB CB
-. ftr VBI CBI
-.\}
 .TH "gemstash-multiple-sources" "7" "October 8, 2015" "" ""
-.hy
 .SH Multiple Gem Sources
-.PP
 Gemstash will stash from any amount of gem sources.
 By the end of this guide, you will be able to bundle using multiple gem
 sources, all stashed within your Gemstash server.
 .SS Default Source
-.PP
 When you don\[cq]t provide an explicit source (as with the Quickstart
 Guide), your gems will be fetched from https://rubygems.org.
 This default source is not set in stone.
 To change it, you need only edit the Gemstash configuration found at
-\f[V]\[ti]/.gemstash/config.yml\f[R]:
+\f[CR]\[ti]/.gemstash/config.yml\f[R]:
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :rubygems_url: https://my.gem-source.local
-\f[R]
-.fi
+.EE
 .PP
 Make sure to restart your Gemstash server after changing the config:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash stop
 $ gemstash start
-\f[R]
-.fi
+.EE
 .PP
-Once restarted, bundling against \f[V]http://localhost:9292\f[R] will
-fetch gems from \f[V]https://my.gem-source.local\f[R].
+Once restarted, bundling against \f[CR]http://localhost:9292\f[R] will
+fetch gems from \f[CR]https://my.gem-source.local\f[R].
 If you had bundled before making these changes, fear not; bundling with
 a different default gem source will store gems in a separate location,
 ensuring different sources won\[cq]t leak between each other.
 .SS Bundling with Multiple Sources
-.PP
 Changing the default source won\[cq]t help you if you need to bundle
 against https://rubygems.org along with additional sources.
 If you need to bundle with multiple gem sources, Gemstash doesn\[cq]t
 need to be specially configured.
 Your Gemstash server will honor any gem source specified via a
 specialized URL.
-Consider the following \f[V]Gemfile\f[R]:
+Consider the following \f[CR]Gemfile\f[R]:
 .IP
-.nf
-\f[C]
+.EX
 # ./Gemfile
 require \[dq]cgi\[dq]
 source \[dq]http://localhost:9292\[dq]
@@ -72,31 +49,27 @@ gem \[dq]rubywarrior\[dq]
 source \[dq]http://localhost:9292/upstream/#{CGI.escape(\[dq]https://my.gem-source.local\[dq])}\[dq] do
   gem \[dq]my-gem\[dq]
 end
-\f[R]
-.fi
+.EE
 .PP
-Notice the \f[V]CGI.escape\f[R] call in the second source.
+Notice the \f[CR]CGI.escape\f[R] call in the second source.
 This is important, as it properly URL escapes the source URL so Gemstash
 knows what gem source you want.
-The \f[V]/upstream\f[R] prefix tells Gemstash to use a gem source other
+The \f[CR]/upstream\f[R] prefix tells Gemstash to use a gem source other
 than the default source.
 You can now bundle with the additional source.
 .SS Redirecting
-.PP
 Gemstash supports an alternate mode of specifying your gem sources.
 If you want Gemstash to redirect Bundler to your given gem sources, then
-you can specify your \f[V]Gemfile\f[R] like so:
+you can specify your \f[CR]Gemfile\f[R] like so:
 .IP
-.nf
-\f[C]
+.EX
 # ./Gemfile
 require \[dq]cgi\[dq]
 source \[dq]http://localhost:9292/redirect/#{CGI.escape(\[dq]https://rubygems.org\[dq])}\[dq]
 gem \[dq]rubywarrior\[dq]
-\f[R]
-.fi
+.EE
 .PP
-Notice the \f[V]/redirect\f[R] prefix.
+Notice the \f[CR]/redirect\f[R] prefix.
 This prefix tells Gemstash to redirect API calls to the provided URL.
 Redirected calls like this will not be cached by Gemstash, and gem files
 will not be stashed, even if they were previously cached or stashed from

data/lib/gemstash/man/gemstash-multiple-sources.7.txt

@@ -11,7 +11,7 @@
        When you don't provide an  explicit  source  (as  with  the  Quickstart
        Guide),	your gems will be fetched from https://rubygems.org.  This de-
        fault source is not set in stone.  To change it, you need only edit the
-       Gemstash configuration found at 1m~/.gemstash/config.yml22m:
+       Gemstash configuration found at ~/.gemstash/config.yml:
 
 	      # ~/.gemstash/config.yml
 	      ---
@@ -22,8 +22,8 @@
 	      $ gemstash stop
 	      $ gemstash start
 
-       Once restarted, bundling against 1mhttp://localhost:9292 22mwill fetch  gems
-       from  1mhttps://my.gem-source.local22m.	 If  you  had bundled before making
+       Once restarted, bundling against http://localhost:9292 will fetch  gems
+       from  https://my.gem-source.local.   If	you  had bundled before making
        these changes, fear not; bundling with a different default  gem	source
        will  store  gems  in  a  separate location, ensuring different sources
        won't leak between each other.
@@ -33,7 +33,7 @@
        against	https://rubygems.org  along  with  additional sources.	If you
        need to bundle with multiple gem sources, Gemstash doesn't need	to  be
        specially  configured.	Your Gemstash server will honor any gem source
-       specified via a specialized URL.  Consider the following 1mGemfile22m:
+       specified via a specialized URL.  Consider the following Gemfile:
 
 	      # ./Gemfile
 	      require "cgi"
@@ -44,23 +44,23 @@
 		gem "my-gem"
 	      end
 
-       Notice the 1mCGI.escape 22mcall in the second source.  This is important, as
+       Notice the CGI.escape call in the second source.  This is important, as
        it properly URL escapes the source  URL	so  Gemstash  knows  what  gem
-       source  you  want.   The  1m/upstream  22mprefix tells Gemstash to use a gem
+       source  you  want.   The  /upstream  prefix tells Gemstash to use a gem
        source other than the default source.  You can now bundle with the  ad-
        ditional source.
 
    1mRedirecting0m
        Gemstash supports an alternate mode of specifying your gem sources.  If
        you  want  Gemstash to redirect Bundler to your given gem sources, then
-       you can specify your 1mGemfile 22mlike so:
+       you can specify your Gemfile like so:
 
 	      # ./Gemfile
 	      require "cgi"
 	      source "http://localhost:9292/redirect/#{CGI.escape("https://rubygems.org")}"
 	      gem "rubywarrior"
 
-       Notice the 1m/redirect 22mprefix.  This prefix tells  Gemstash  to  redirect
+       Notice the /redirect prefix.  This prefix tells	Gemstash  to  redirect
        API  calls to the provided URL.	Redirected calls like this will not be
        cached by Gemstash, and gem files will not be  stashed,	even  if  they
        were previously cached or stashed from the same gem source.

data/lib/gemstash/man/gemstash-private-gems.7

@@ -1,24 +1,8 @@
 <!-- Automatically generated by Pandoc -->
-.\" Automatically generated by Pandoc 3.1.6.2
+.\" Automatically generated by Pandoc 3.1.8
 .\"
-.\" Define V font for inline verbatim, using C font in formats
-.\" that render this, and otherwise B font.
-.ie "\f[CB]x\f[]"x" \{\
-. ftr V B
-. ftr VI BI
-. ftr VB B
-. ftr VBI BI
-.\}
-.el \{\
-. ftr V CR
-. ftr VI CI
-. ftr VB CB
-. ftr VBI CBI
-.\}
 .TH "gemstash-private-gems" "7" "October 8, 2015" "" ""
-.hy
 .SH Private Gems
-.PP
 Stashing private gems in your Gemstash server requires a bit of
 additional setup.
 If you haven\[cq]t read through the Quickstart Guide, you should do that
@@ -26,7 +10,6 @@ first.
 By the end of this guide, you will be able to interact with your
 Gemstash server to store and retrieve your private gems.
 .SS Authorizing
-.PP
 \f[B]IMPORTANT NOTE:\f[R] Do not use the actual key value in this
 document, otherwise your Gemstash server will be vulnerable to anyone
 who wants to try to use the key against your server.
@@ -35,38 +18,32 @@ running the commands.
 .PP
 In order to push a gem to your Gemstash server, you need to first create
 an API key.
-Utilize the \f[V]gemstash authorize\f[R] command to create the API key:
+Utilize the \f[CR]gemstash authorize\f[R] command to create the API key:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash authorize
 Your new key is: e374e237fdf5fa5718d2a21bd63dc911
-\f[R]
-.fi
+.EE
 .PP
-This new key can \f[V]push\f[R], \f[V]yank\f[R], and \f[V]fetch\f[R]
+This new key can \f[CR]push\f[R], \f[CR]yank\f[R], and \f[CR]fetch\f[R]
 gems from your Gemstash server.
-Run \f[V]gemstash authorize\f[R] with just the permissions you want to
+Run \f[CR]gemstash authorize\f[R] with just the permissions you want to
 limit what the key will be allowed to do.
 You can similarly update a specific key by providing it via the
-\f[V]--key\f[R] option:
+\f[CR]--key\f[R] option:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash authorize push yank --key e374e237fdf5fa5718d2a21bd63dc911
-\f[R]
-.fi
+.EE
 .PP
 When no permissions are provided (like the first example), the key will
 be authorized for all permissions.
 Leave the key authorized with everything if you want to use it to try
 all private gem interactions:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash authorize --key e374e237fdf5fa5718d2a21bd63dc911
-\f[R]
-.fi
+.EE
 .PP
 With the key generated, you\[cq]ll need to tell Rubygems about your new
 key.
@@ -75,86 +52,70 @@ already have a credentials file to add the key to.
 If not, run the following commands before modifying the credentials
 file:
 .IP
-.nf
-\f[C]
+.EX
 $ mkdir -p \[ti]/.gem
 $ touch \[ti]/.gem/credentials
 $ chmod 0600 \[ti]/.gem/credentials
-\f[R]
-.fi
+.EE
 .PP
 Add your new key to credentials such that it looks something like this
 (but make sure not to remove any existing keys):
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gem/credentials
 ---
 :test_key: e374e237fdf5fa5718d2a21bd63dc911
-\f[R]
-.fi
+.EE
 .PP
-The name \f[V]test_key\f[R] can be anything you want, but you will need
+The name \f[CR]test_key\f[R] can be anything you want, but you will need
 to remember it and use it again later in this guide for the
-\f[V]--key\f[R] option.
+\f[CR]--key\f[R] option.
 .SS Creating a Test Gem
-.PP
 You\[cq]ll need a test gem before you can play with private gems on your
 Gemstash server.
 If you have a gem you can use, move along to the next section.
 You can start by instantiating a test gem via Bundler:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle gem private-example
-\f[R]
-.fi
+.EE
 .PP
 You\[cq]ll need to add a summary and description to the new gem\[cq]s
 gemspec file in order to successfully build it.
 Once you\[cq]ve built the gem, you will be ready to push the new gem.
 .IP
-.nf
-\f[C]
+.EX
 $ cd private-example
 $ rake build
-\f[R]
-.fi
+.EE
 .PP
 You will now have a gem at
-\f[V]private-example/pkg/private-example-0.1.0.gem\f[R].
+\f[CR]private-example/pkg/private-example-0.1.0.gem\f[R].
 .SS Pushing
-.PP
 If your Gemstash server isn\[cq]t running, go ahead and start it:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash start
-\f[R]
-.fi
+.EE
 .PP
 Push your test gem using Rubygems:
 .IP
-.nf
-\f[C]
+.EX
 $ gem push --key test_key --host http://localhost:9292/private pkg/private-example-0.1.0.gem
-\f[R]
-.fi
+.EE
 .PP
-The \f[V]/private\f[R] portion of the \f[V]--host\f[R] option tells
+The \f[CR]/private\f[R] portion of the \f[CR]--host\f[R] option tells
 Gemstash you are interacting with the private gems.
 Gemstash will not let you push, or yank from anything except
-\f[V]/private\f[R].
+\f[CR]/private\f[R].
 .SS Bundling
-.PP
 Once your gem is pushed to your Gemstash server, you are ready to bundle
 it.
-Create a \f[V]Gemfile\f[R] and specify the gem.
+Create a \f[CR]Gemfile\f[R] and specify the gem.
 You will probably want to wrap the private gem in a source block, and
 let the rest of Gemstash handle all other gems:
 .IP
-.nf
-\f[C]
+.EX
 # ./Gemfile
 source \[dq]http://localhost:9292\[dq]
 gem \[dq]rubywarrior\[dq]
@@ -162,65 +123,55 @@ gem \[dq]rubywarrior\[dq]
 source \[dq]http://localhost:9292/private\[dq] do
   gem \[dq]private-example\[dq]
 end
-\f[R]
-.fi
+.EE
 .PP
-Notice that the Gemstash server points to \f[V]/private\f[R] again when
+Notice that the Gemstash server points to \f[CR]/private\f[R] again when
 installing your private gem.
 Go ahead and bundle to install your new private gem:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle
-\f[R]
-.fi
+.EE
 .SS Yanking
-.PP
 If you push a private gem by accident, you can yank the gem with
 Rubygems:
 .IP
-.nf
-\f[C]
+.EX
 $ RUBYGEMS_HOST=http://localhost:9292/private gem yank --key test_key private-example --version 0.1.0
-\f[R]
-.fi
+.EE
 .PP
-Like with pushing, the \f[V]/private\f[R] portion of the host option
+Like with pushing, the \f[CR]/private\f[R] portion of the host option
 tells Gemstash you are interacting with private gems.
-Gemstash will only let you yank from \f[V]/private\f[R].
-Unlike pushing, Rubygems doesn\[cq]t support \f[V]--host\f[R] for yank
-(yet), so you need to specify the host via the \f[V]RUBYGEMS_HOST\f[R]
+Gemstash will only let you yank from \f[CR]/private\f[R].
+Unlike pushing, Rubygems doesn\[cq]t support \f[CR]--host\f[R] for yank
+(yet), so you need to specify the host via the \f[CR]RUBYGEMS_HOST\f[R]
 environment variable.
 .SS Protected Fetching
-.PP
 By default, private gems and specs can be accessed without
 authentication.
 .PP
 Private gems often require protected fetching.
 For backwards compatibility this is disabled by default, but can be
-enabled via \f[V]$ gemstash setup\f[R] command.
+enabled via \f[CR]$ gemstash setup\f[R] command.
 .PP
 When protected fetching is enabled API keys with the permissions
-\f[V]all\f[R] or \f[V]fetch\f[R] can be used to download gems and specs.
+\f[CR]all\f[R] or \f[CR]fetch\f[R] can be used to download gems and
+specs.
 .PP
 On the Bundler side, there are a few ways to configure credentials for a
 given gem source:
 .PP
 Add credentials globally:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config my-gemstash.dev api_key
-\f[R]
-.fi
+.EE
 .PP
 Add credentials in Gemfile:
 .IP
-.nf
-\f[C]
+.EX
 source \[dq]https://api_key\[at]my-gemstash.dev\[dq]
-\f[R]
-.fi
+.EE
 .PP
 However, it\[cq]s not a good practice to commit credentials to source
 control.
@@ -228,15 +179,13 @@ A recommended solution is to use Bundler\[cq]s configuration
 keys (http://bundler.io/man/bundle-config.1.html#CONFIGURATION-KEYS),
 e.g.:
 .IP
-.nf
-\f[C]
+.EX
 $ export BUNDLE_MYGEMSTASH__DEV=api_key
-\f[R]
-.fi
+.EE
 .PP
 Behind the scene, Bundler will pick up the ENV var according to the host
-name (e.g.\ mygemstash.dev) and add to \f[V]URI.userinfo\f[R] for making
-requests.
+name (e.g.\ mygemstash.dev) and add to \f[CR]URI.userinfo\f[R] for
+making requests.
 .PP
 The API key is treated as a HTTP Basic Auth username and any HTTP Basic
 password supplied will be ignored.