gemstash 2.2.2 → 2.7.1

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

@@ -1,24 +1,8 @@
 <!-- Automatically generated by Pandoc -->
-.\" Automatically generated by Pandoc 3.1
+.\" 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.

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

@@ -1,6 +1,4 @@
-gemstash-private-gems(7)			      gemstash-private-gems(7)
-
-
+4mgemstash-private-gems24m(7)				   4mgemstash-private-gems24m(7)
 
 <!-- Automatically generated by Pandoc -->
 
@@ -17,44 +15,44 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
        try to use the key against your server.	Instead of the key value here,
        use whatever key is generated from running the commands.
 
-       In order to push a gem to your Gemstash server, you need to first  cre-
-       ate  an	API key.  Utilize the 1mgemstash authorize 22mcommand to create the
+       In  order to push a gem to your Gemstash server, you need to first cre-
+       ate an API key.	Utilize the gemstash authorize command to  create  the
        API key:
 
 	      $ gemstash authorize
 	      Your new key is: e374e237fdf5fa5718d2a21bd63dc911
 
-       This new key can 1mpush22m, 1myank22m, and 1mfetch 22mgems from your Gemstash  server.
-       Run 1mgemstash authorize 22mwith just the permissions you want to limit what
+       This  new key can push, yank, and fetch gems from your Gemstash server.
+       Run gemstash authorize 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 1m--key 22moption:
+       by providing it via the --key option:
 
 	      $ gemstash authorize push yank --key e374e237fdf5fa5718d2a21bd63dc911
 
        When no permissions are provided (like the first example), the key will
-       be authorized for all permissions.  Leave the key authorized  with  ev-
-       erything if you want to use it to try all private gem interactions:
+       be authorized for all  permissions.   Leave  the  key  authorized  with
+       everything if you want to use it to try all private gem interactions:
 
 	      $ gemstash authorize --key e374e237fdf5fa5718d2a21bd63dc911
 
        With  the  key  generated,  you'll need to tell Rubygems about your new
        key.  If you've pushed a gem to https://rubygems.org, then you will al-
-       ready  have a credentials file to add the key to.  If not, run the fol-
+       ready have a credentials file to add the key to.  If not, run the  fol-
        lowing commands before modifying the credentials file:
 
 	      $ mkdir -p ~/.gem
 	      $ touch ~/.gem/credentials
 	      $ chmod 0600 ~/.gem/credentials
 
-       Add your new key to credentials such that it looks something like  this
+       Add  your new key to credentials such that it looks something like this
        (but make sure not to remove any existing keys):
 
 	      # ~/.gem/credentials
 	      ---
 	      :test_key: e374e237fdf5fa5718d2a21bd63dc911
 
-       The name 1mtest_key 22mcan be anything you want, but you will need to remem-
-       ber it and use it again later in this guide for the 1m--key 22moption.
+       The name test_key can be anything you want, but you will need to remem-
+       ber it and use it again later in this guide for the --key option.
 
    1mCreating a Test Gem0m
        You'll need a test gem before you can play with private	gems  on  your
@@ -63,15 +61,15 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 	      $ bundle gem private-example
 
-       You'll need to add a summary and description to the new	gem's  gemspec
+       You'll  need  to add a summary and description to the new gem's gemspec
        file in order to successfully build it.	Once you've built the gem, you
        will be ready to push the new gem.
 
 	      $ cd private-example
 	      $ rake build
 
-       You  will  now  have   a   gem	at   1mprivate-example/pkg/private-exam-0m
-       1mple-0.1.0.gem22m.
+       You  will  now  have   a   gem	at   private-example/pkg/private-exam-
+       ple-0.1.0.gem.
 
    1mPushing0m
        If your Gemstash server isn't running, go ahead and start it:
@@ -82,13 +80,13 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 	      $ gem push --key test_key --host http://localhost:9292/private pkg/private-example-0.1.0.gem
 
-       The 1m/private 22mportion of the 1m--host 22moption tells Gemstash you are inter-
-       acting with the private gems.  Gemstash will not let you push, or  yank
-       from anything except 1m/private22m.
+       The /private portion of the --host option tells Gemstash you are inter-
+       acting  with the private gems.  Gemstash will not let you push, or yank
+       from anything except /private.
 
    1mBundling0m
-       Once  your gem is pushed to your Gemstash server, you are ready to bun-
-       dle it.	Create a 1mGemfile 22mand specify the gem.  You will probably  want
+       Once your gem is pushed to your Gemstash server, you are ready to  bun-
+       dle  it.  Create a Gemfile 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:
 
@@ -100,7 +98,7 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 		gem "private-example"
 	      end
 
-       Notice that the Gemstash server	points	to  1m/private	22magain  when	in-
+       Notice that the Gemstash server	points	to  /private  again  when  in-
        stalling  your  private	gem.   Go ahead and bundle to install your new
        private gem:
 
@@ -112,24 +110,24 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 	      $ RUBYGEMS_HOST=http://localhost:9292/private gem yank --key test_key private-example --version 0.1.0
 
-       Like  with  pushing, the 1m/private 22mportion of the host option tells Gem-
+       Like  with  pushing, the /private portion of the host option tells Gem-
        stash you are interacting with private gems.  Gemstash  will  only  let
-       you  yank  from	1m/private22m.	 Unlike  pushing,  Rubygems doesn't support
-       1m--host 22mfor yank (yet),  so	you  need  to  specify	the  host  via	the
-       1mRUBYGEMS_HOST 22menvironment variable.
+       you  yank  from	/private.   Unlike  pushing,  Rubygems doesn't support
+       --host for yank (yet),  so  you	need  to  specify  the	host  via  the
+       RUBYGEMS_HOST environment variable.
 
    1mProtected Fetching0m
        By  default, private gems and specs can be accessed without authentica-
        tion.
 
        Private gems often require protected fetching.  For backwards  compati-
-       bility  this  is disabled by default, but can be enabled via 1m$ gemstash0m
-       1msetup 22mcommand.
+       bility  this  is disabled by default, but can be enabled via $ gemstash
+       setup command.
 
-       When protected fetching is enabled API keys with the permissions 1mall 22mor
-       1mfetch 22mcan be used to download gems and specs.
+       When protected fetching is enabled API keys with the permissions all or
+       fetch can be used to download gems and specs.
 
-       On  the Bundler side, there are a few ways to configure credentials for
+       On the Bundler side, there are a few ways to configure credentials  for
        a given gem source:
 
        Add credentials globally:
@@ -140,19 +138,17 @@ gemstash-private-gems(7)			      gemstash-private-gems(7)
 
 	      source "https://api_key@my-gemstash.dev"
 
-       However, it's not a good practice to commit credentials to source  con-
-       trol.   A  recommended  solution is to use Bundler's configuration keys
+       However,  it's not a good practice to commit credentials to source con-
+       trol.  A recommended solution is to use	Bundler's  configuration  keys
        (http://bundler.io/man/bundle-config.1.html#CONFIGURATION-KEYS), e.g.:
 
 	      $ export BUNDLE_MYGEMSTASH__DEV=api_key
 
-       Behind the scene, Bundler will pick up the ENV  var  according  to  the
-       host  name (e.g. mygemstash.dev) and add to 1mURI.userinfo 22mfor making re-
+       Behind  the  scene,  Bundler  will pick up the ENV var according to the
+       host name (e.g. mygemstash.dev) and add to URI.userinfo for making  re-
        quests.
 
        The API key is treated as a HTTP Basic Auth username and any HTTP Basic
        password supplied will be ignored.
 
-
-
-				October 8, 2015       gemstash-private-gems(7)
+				October 8, 2015       4mgemstash-private-gems24m(7)