gemstash 2.1.0 → 2.2.1

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

@@ -1,11 +1,26 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-deploy" "7" "October 25, 2015" "" ""
+.\" 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-deploy" "7" "October 25, 2015" "" ""
 .hy
-.SH DEPLOYING GEMSTASH
+.SH Deploying Gemstash
 .PP
-Bundler is here for the rescue to keep Gemstash up to date! Create a
-\f[C]Gemfile\f[R] pointing to Gemstash:
+Bundler is here for the rescue to keep Gemstash up to date!
+Create a \f[V]Gemfile\f[R] pointing to Gemstash:
 .IP
 .nf
 \f[C]
@@ -15,11 +30,11 @@ gem \[dq]gemstash\[dq]
 \f[R]
 .fi
 .PP
-Then \f[C]bundle\f[R] to create your \f[C]Gemfile.lock\f[R].
-When you are ready to upgrade, simply \f[C]bundle update\f[R].
-You may need to run \f[C]gemstash\f[R] via \f[C]bundle exec\f[R].
-Alternatively, you can \f[C]gem uninstall gemstash\f[R] and
-\f[C]gem install gemstash\f[R] when you want to upgrade.
+Then \f[V]bundle\f[R] to create your \f[V]Gemfile.lock\f[R].
+When you are ready to upgrade, simply \f[V]bundle update\f[R].
+You may need to run \f[V]gemstash\f[R] via \f[V]bundle exec\f[R].
+Alternatively, you can \f[V]gem uninstall gemstash\f[R] and
+\f[V]gem install gemstash\f[R] when you want to upgrade.
 .PP
 Gemstash will automatically run any necessary migrations, so updating
 the gem is all that needs to be done.
@@ -34,12 +49,12 @@ $ bundle update
 $ bundle exec gemstash start
 \f[R]
 .fi
-.SS MONITORING
+.SS Monitoring
 .PP
 Health monitoring is built in to Gemstash using the
-server_health_check\-rack (https://github.com/on-site/server_health_check-rack)
+server_health_check-rack (https://github.com/on-site/server_health_check-rack)
 gem.
-If you request \f[C]/health\f[R] from your Gemstash instance, you will
+If you request \f[V]/health\f[R] from your Gemstash instance, you will
 get a JSON response along with an HTTP status code indicating success or
 failure.
 The JSON response will look something like this for a success case:
@@ -63,10 +78,10 @@ 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\[cq]t interact
-with storage or the database, you can use \f[C]/health/heartbeat\f[R]
+with storage or the database, you can use \f[V]/health/heartbeat\f[R]
 which will always respond with a success while your Gemstash server is
 running.
-.SS DOWNGRADING
+.SS Downgrading
 .PP
 It is not recommended to go backwards in Gemstash versions.
 Migrations may have run that could leave the database in a bad state.

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

@@ -2,20 +2,22 @@ gemstash-deploy(7)					    gemstash-deploy(7)
 
 
 
-1mDEPLOYING GEMSTASH0m
-       Bundler	is  here  for the rescue to keep Gemstash up to date! Create a
-       Gemfile pointing to Gemstash:
+<!-- Automatically generated by Pandoc -->
+
+1mDeploying Gemstash0m
+       Bundler	is  here for the rescue to keep Gemstash up to date!  Create a
+       1mGemfile 22mpointing to Gemstash:
 
 	      # ./Gemfile
 	      source "https://rubygems.org"
 	      gem "gemstash"
 
-       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.
+       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.
 
-       Gemstash	 will  automatically run any necessary migrations, so updating
+       Gemstash  will  automatically run any necessary migrations, so updating
        the gem is all that needs to be done.
 
        It is probably wise to stop Gemstash before  upgrading,	then  starting
@@ -25,12 +27,12 @@ gemstash-deploy(7)					    gemstash-deploy(7)
 	      $ bundle update
 	      $ bundle exec gemstash start
 
-   1mMONITORING0m
-       Health	monitoring   is	  built	  in   to  Gemstash  using  the	 serv-
+   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 /health from your Gemstash instance, you
+       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
+       cess or failure.  The JSON response will look something like this for a
        success case:
 
 	      {
@@ -46,14 +48,14 @@ gemstash-deploy(7)					    gemstash-deploy(7)
        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
+       doesn't	 interact   with   storage   or  the  database,  you  can  use
+       1m/health/heartbeat 22mwhich will always respond with a success	while  your
        Gemstash server is running.
 
-   1mDOWNGRADING0m
+   1mDowngrading0m
        It is not recommended to go backwards in Gemstash versions.  Migrations
        may have run that could leave the database in a bad state.
 
 
 
-			       October 25, 2015		    gemstash-deploy(7)
+			       October 25, 2015 	    gemstash-deploy(7)

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

@@ -1,38 +1,53 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-mirror" "7" "October 25, 2015" "" ""
+.\" 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
+.SH Using Gemstash as a Mirror
 .PP
-If you don\[cq]t have control over your \f[C]Gemfile\f[R], or you
+If you don\[cq]t have control over your \f[V]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[C]Gemfile\f[R], add a mirror pointing to your
+For each source in your \f[V]Gemfile\f[R], add a mirror pointing to your
 Gemstash server:
 .IP
 .nf
 \f[C]
 $ 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])
+$ 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
 .PP
 From now on, bundler will fetch gems from those sources via your
 Gemstash server.
-.SH SIMPLER GEMSTASH MIRRORS
+.SH Simpler Gemstash Mirrors
 .PP
 \f[B]This feature requires Bundler to be at least version
-\f[CB]1.11.0\f[B].\f[R]
+\f[VB]1.11.0\f[B].\f[R]
 .PP
-If you are using Bundler version \f[C]1.11.0\f[R] or greater, the
+If you are using Bundler version \f[V]1.11.0\f[R] or greater, the
 mirroring becomes a bit easier:
 .IP
 .nf
 \f[C]
 $ bundle config mirror.http://rubygems.org http://localhost:9292
-$ bundle config mirror.https://my.gem\-source.local http://localhost:9292
+$ bundle config mirror.https://my.gem-source.local http://localhost:9292
 \f[R]
 .fi
 .PP

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

@@ -2,12 +2,14 @@ gemstash-mirror(7)					    gemstash-mirror(7)
 
 
 
-1mUSING GEMSTASH AS A MIRROR0m
-       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
+<!-- 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
+       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 Gemfile, add a mirror pointing to your Gemstash
+       For each source in your 1mGemfile22m, add a mirror pointing to your Gemstash
        server:
 
 	      $ bundle config mirror.http://rubygems.org http://localhost:9292
@@ -16,10 +18,10 @@ gemstash-mirror(7)					    gemstash-mirror(7)
        From now on, bundler will fetch gems from those sources via  your  Gem-
        stash server.
 
-1mSIMPLER GEMSTASH MIRRORS0m
+1mSimpler Gemstash Mirrors0m
        1mThis feature requires Bundler to be at least version 1.11.0.0m
 
-       If  you	are using Bundler version 1.11.0 or greater, the mirroring be-
+       If  you	are using Bundler version 1m1.11.0 22mor greater, the mirroring be-
        comes a bit easier:
 
 	      $ bundle config mirror.http://rubygems.org http://localhost:9292
@@ -30,4 +32,4 @@ gemstash-mirror(7)					    gemstash-mirror(7)
 
 
 
-			       October 25, 2015		    gemstash-mirror(7)
+			       October 25, 2015 	    gemstash-mirror(7)

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

@@ -1,26 +1,40 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-multiple\-sources" "7" "October 8, 2015" "" ""
+.\" 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
+.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
+.SS Default Source
 .PP
 When you don\[cq]t provide an explicit source (as with the Quickstart
-Guide (../readme.md#quickstart-guide)), your gems will be fetched from
-https://rubygems.org.
+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[C]\[ti]/.gemstash/config.yml\f[R]:
+\f[V]\[ti]/.gemstash/config.yml\f[R]:
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
-:rubygems_url: https://my.gem\-source.local
+---
+:rubygems_url: https://my.gem-source.local
 \f[R]
 .fi
 .PP
@@ -33,12 +47,12 @@ $ gemstash start
 \f[R]
 .fi
 .PP
-Once restarted, bundling against \f[C]http://localhost:9292\f[R] will
-fetch gems from \f[C]https://my.gem\-source.local\f[R].
+Once restarted, bundling against \f[V]http://localhost:9292\f[R] will
+fetch gems from \f[V]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
+.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.
@@ -46,7 +60,7 @@ 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[C]Gemfile\f[R]:
+Consider the following \f[V]Gemfile\f[R]:
 .IP
 .nf
 \f[C]
@@ -55,23 +69,23 @@ require \[dq]cgi\[dq]
 source \[dq]http://localhost:9292\[dq]
 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]
+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
 .PP
-Notice the \f[C]CGI.escape\f[R] call in the second source.
+Notice the \f[V]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[C]/upstream\f[R] prefix tells Gemstash to use a gem source other
+The \f[V]/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
+.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[C]Gemfile\f[R] like so:
+you can specify your \f[V]Gemfile\f[R] like so:
 .IP
 .nf
 \f[C]
@@ -82,7 +96,7 @@ gem \[dq]rubywarrior\[dq]
 \f[R]
 .fi
 .PP
-Notice the \f[C]/redirect\f[R] prefix.
+Notice the \f[V]/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

@@ -2,17 +2,18 @@ gemstash-multiple-sources(7)			  gemstash-multiple-sources(7)
 
 
 
-1mMULTIPLE GEM SOURCES0m
+<!-- Automatically generated by Pandoc -->
+
+1mMultiple Gem Sources0m
        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
+       guide, you will be able to  bundle  using  multiple  gem  sources,  all
        stashed within your Gemstash server.
 
-   1mDEFAULT SOURCE0m
-       When you don't provide an explicit source (as with the Quickstart Guide
-       (../readme.md#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
-       ~/.gemstash/config.yml:
+   1mDefault Source0m
+       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/config.yml
 	      ---
@@ -23,18 +24,18 @@ gemstash-multiple-sources(7)			  gemstash-multiple-sources(7)
 	      $ gemstash stop
 	      $ gemstash start
 
-       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
+       Once restarted, bundling against 1mhttp://localhost:9292 22mwill fetch  gems
+       from  1mhttps://my.gem-source.local22m.	 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.
 
-   1mBUNDLING WITH MULTIPLE SOURCES0m
-       Changing	 the  default  source  won'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't need to be
-       specially configured.  Your Gemstash server will honor any  gem	source
-       specified via a specialized URL.	 Consider the following Gemfile:
+   1mBundling with Multiple Sources0m
+       Changing the default source won'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't need	to  be
+       specially  configured.	Your Gemstash server will honor any gem source
+       specified via a specialized URL.  Consider the following 1mGemfile22m:
 
 	      # ./Gemfile
 	      require "cgi"
@@ -45,27 +46,27 @@ gemstash-multiple-sources(7)			  gemstash-multiple-sources(7)
 		gem "my-gem"
 	      end
 
-       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	 /upstream  prefix tells Gemstash to use a gem
-       source other than the default source.  You can now bundle with the  ad-
+       Notice the 1mCGI.escape 22mcall 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  other than the default source.  You can now bundle with the ad-
        ditional source.
 
-   1mREDIRECTING0m
+   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 Gemfile like so:
+       you  want  Gemstash to redirect Bundler to your given gem sources, then
+       you can specify your 1mGemfile 22mlike so:
 
 	      # ./Gemfile
 	      require "cgi"
 	      source "http://localhost:9292/redirect/#{CGI.escape("https://rubygems.org")}"
 	      gem "rubywarrior"
 
-       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
+       Notice the 1m/redirect 22mprefix.  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.
 
 
 
-				October 8, 2015	  gemstash-multiple-sources(7)
+				October 8, 2015   gemstash-multiple-sources(7)