gemstash 2.3.2 → 2.4.0

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

@@ -1,34 +1,17 @@
 <!-- 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-customize" "7" "October 28, 2015" "" ""
-.hy
 .SH Customizing the Server
-.PP
 Although Gemstash is designed for as minimal setup as possible, there
 may be times you will want to change some of the default configuration.
 By the end of this guide, you will be able to customize some of the
 Gemstash behavior, including where files are stored, what database
 Gemstash uses, and how Gemstash caches certain requests.
 .SS Setup
-.PP
 Several customizable options are available via an interactive Gemstash
 command.
-Run \f[V]gemstash setup\f[R] and answer the questions it provides (a
+Run \f[CR]gemstash setup\f[R] and answer the questions it provides (a
 blank answer will use the default value):
 .RS
 .PP
@@ -79,11 +62,11 @@ Once you\[cq]ve answered the questions, some checks will be made to
 ensure the configuration will work.
 For example, the database didn\[cq]t exist in the previous example, so
 the command failed and the configuration wasn\[cq]t saved.
-If the command passes, you may provide the \f[V]--redo\f[R] option to
+If the command passes, you may provide the \f[CR]--redo\f[R] option to
 force configuration to be redone:
 .RS
 .PP
-\f[V]$ gemstash setup --redo\f[R]
+\f[CR]$ gemstash setup --redo\f[R]
 .PD 0
 .P
 .PD
@@ -122,46 +105,41 @@ You are all setup!
 .RE
 .PP
 Once all checks have passed, Gemstash will store your answers in the
-configuration file located at \f[V]\[ti]/.gemstash/config.yml\f[R].
+configuration file located at \f[CR]\[ti]/.gemstash/config.yml\f[R].
 .SS Files
-.PP
-Storage in Gemstash defaults to \f[V]\[ti]/.gemstash\f[R] unless
+Storage in Gemstash defaults to \f[CR]\[ti]/.gemstash\f[R] unless
 otherwise specified.
-You can change this in your config file via the \f[V]:base_path\f[R]
+You can change this in your config file via the \f[CR]:base_path\f[R]
 key:
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :base_path: \[dq]/var/gemstash\[dq]
-\f[R]
-.fi
+.EE
 .PP
-When customizing the \f[V]base_path\f[R], the directory must exist,
+When customizing the \f[CR]base_path\f[R], the directory must exist,
 otherwise Gemstash will fail to run.
-Thus, if you want to use \f[V]/var/gemstash\f[R] like in the previous
-example, make sure to \f[V]mkdir /var/gemstash\f[R] and grant access to
+Thus, if you want to use \f[CR]/var/gemstash\f[R] like in the previous
+example, make sure to \f[CR]mkdir /var/gemstash\f[R] and grant access to
 the directory for the user you run Gemstash with.
 .SS Database
-.PP
-The \f[V]:db_adapter\f[R] configuration key specifies what database you
+The \f[CR]:db_adapter\f[R] configuration key specifies what database you
 will be using.
-The default \f[V]:db_adapter\f[R] is
-\f[V]sqlite3\f[R] (https://www.sqlite.org/), which will use a database
-file located within your \f[V]:base_path\f[R].
-The database file will always be named \f[V]gemstash.db\f[R].
+The default \f[CR]:db_adapter\f[R] is
+\f[CR]sqlite3\f[R] (https://www.sqlite.org/), which will use a database
+file located within your \f[CR]:base_path\f[R].
+The database file will always be named \f[CR]gemstash.db\f[R].
 .PP
-You may also use \f[V]postgres\f[R] (http://www.postgresql.org/),
-\f[V]mysql\f[R] (http://www.mysql.com/), or
-\f[V]mysql2\f[R] (http://sequel.jeremyevans.net/rdoc/files/doc/opening_databases_rdoc.html#label-mysql2)
-for your \f[V]:db_adapter\f[R].
+You may also use \f[CR]postgres\f[R] (http://www.postgresql.org/),
+\f[CR]mysql\f[R] (http://www.mysql.com/), or
+\f[CR]mysql2\f[R] (http://sequel.jeremyevans.net/rdoc/files/doc/opening_databases_rdoc.html#label-mysql2)
+for your \f[CR]:db_adapter\f[R].
 When using any of these options, you need to specify the
-\f[V]:db_url\f[R] to point to an existing database.
-Here is an example configuration to use the \f[V]postgres\f[R] adapter:
+\f[CR]:db_url\f[R] to point to an existing database.
+Here is an example configuration to use the \f[CR]postgres\f[R] adapter:
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :db_adapter: postgres
@@ -170,57 +148,50 @@ Here is an example configuration to use the \f[V]postgres\f[R] adapter:
   :connect_timeout: 10
   :read_timeout: 5
   :timeout: 30
-\f[R]
-.fi
+.EE
 .PP
 Regardless of the adapter you choose, the database will automatically
 migrate to your version of Gemstash whenever the database is needed.
 You only need to ensure the database exists and Gemstash will do the
-rest, except for \f[V]sqlite3\f[R] (for which Gemstash will also create
+rest, except for \f[CR]sqlite3\f[R] (for which Gemstash will also create
 the database for you).
 .SS Cache
-.PP
 Certain things (like dependencies) are cached in memory.
 This avoids web calls to the gem source, and database calls for private
 gems.
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :cache_type: memory
 :cache_max_size: 2000
-\f[R]
-.fi
+.EE
 .PP
-This configuration uses the default \f[V]memory\f[R] cache, and has
-increased the \f[V]cache_max_size\f[R] setting from its default of 500
+This configuration uses the default \f[CR]memory\f[R] cache, and has
+increased the \f[CR]cache_max_size\f[R] setting from its default of 500
 items.
 .PP
 The memory cache can optionally be swapped out with a
 Memcached (http://memcached.org/) server (or cluster of servers).
 .PP
-To use Memcached, use the \f[V]memcached\f[R] \f[V]:cache_type\f[R]
+To use Memcached, use the \f[CR]memcached\f[R] \f[CR]:cache_type\f[R]
 configuration.
 .PP
 Provide the servers as a comma-separated list to the
-\f[V]:memcached_servers\f[R] configuration key:
+\f[CR]:memcached_servers\f[R] configuration key:
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :cache_type: memcached
 :memcached_servers: memcached1.local:11211,memcached2.local:11211
 :cache_expiration: 1800
-\f[R]
-.fi
+.EE
 .PP
-All caching expires in \f[V]cache_expiration\f[R] number of seconds.
+All caching expires in \f[CR]cache_expiration\f[R] number of seconds.
 Default is 1800 seconds (30 minutes).
 This option applies to all caching.
 .SS Server
-.PP
 Gemstash uses Puma (http://puma.io/) and Rack (http://rack.github.io/)
 as the server.
 Alternate server configurations are not currently supported, but you can
@@ -232,85 +203,71 @@ for inspiration.
 .PP
 While the server is not customizable, the way Gemstash binds the port
 can be changed.
-To change the binding, update the \f[V]:bind\f[R] configuration key:
+To change the binding, update the \f[CR]:bind\f[R] configuration key:
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :bind: tcp://0.0.0.0:4242
-\f[R]
-.fi
+.EE
 .PP
 This maps directly to the Puma bind
 flag (https://github.com/puma/puma#binding-tcp--sockets), and will
 support anything valid for that flag.
 .PP
 The number of threads Puma uses is also customizable via the
-\f[V]:puma_threads\f[R] configuration key.
-The default is \f[V]16\f[R].
+\f[CR]:puma_threads\f[R] configuration key.
+The default is \f[CR]16\f[R].
 .SS Protected Fetch
-.PP
 Gemstash by default allows unauthenticated access for private gems.
-Authenticated access is available via the \f[V]:protected_fetch\f[R]
+Authenticated access is available via the \f[CR]:protected_fetch\f[R]
 configuration key.
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml
 ---
 :protected_fetch: true
-\f[R]
-.fi
+.EE
 .PP
 More details on protected_fetch are here.
 .SS Fetch Timeout
-.PP
 The default fetch timeout is 20 seconds.
-Use the \f[V]:fetch_timeout\f[R] configuration key to change it.
+Use the \f[CR]:fetch_timeout\f[R] configuration key to change it.
 .IP
-.nf
-\f[C]
+.EX
 ---
 :fetch_timeout: 20
-\f[R]
-.fi
+.EE
 .SS Config File Location
-.PP
 By default, configuration for Gemstash will be at
-\f[V]\[ti]/.gemstash/config.yml\f[R].
-This can be changed by providing the \f[V]--config-file\f[R] option to
+\f[CR]\[ti]/.gemstash/config.yml\f[R].
+This can be changed by providing the \f[CR]--config-file\f[R] option to
 the various Gemstash commands:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash setup --config-file ./gemstash-config.yml
 $ gemstash authorize --config-file ./gemstash-config.yml
 $ gemstash start --config-file ./gemstash-config.yml
 $ gemstash stop --config-file ./gemstash-config.yml
 $ gemstash status --config-file ./gemstash-config.yml
-\f[R]
-.fi
+.EE
 .PP
-When providing \f[V]--config-file\f[R] to \f[V]gemstash setup\f[R], the
-provided file will be output to with the provided configuration.
+When providing \f[CR]--config-file\f[R] to \f[CR]gemstash setup\f[R],
+the provided file will be output to with the provided configuration.
 \f[B]This will overwrite\f[R] any existing configuration.
-If the file doesn\[cq]t exist when providing \f[V]--config-file\f[R] to
-\f[V]gemstash start\f[R], \f[V]gemstash stop\f[R],
-\f[V]gemstash status\f[R], and \f[V]gemstash authorize\f[R], the default
-configuration will be used.
+If the file doesn\[cq]t exist when providing \f[CR]--config-file\f[R] to
+\f[CR]gemstash start\f[R], \f[CR]gemstash stop\f[R],
+\f[CR]gemstash status\f[R], and \f[CR]gemstash authorize\f[R], the
+default configuration will be used.
 .SS ERB parsed config
-.PP
-You may also create a \f[V]\[ti]/.gemstash/config.yml.erb\f[R] file.
+You may also create a \f[CR]\[ti]/.gemstash/config.yml.erb\f[R] file.
 If present, this will be used instead of
-\f[V]\[ti]/.gemstash/config.yml\f[R].
+\f[CR]\[ti]/.gemstash/config.yml\f[R].
 For example, with this you can use environment variables in the config:
 .IP
-.nf
-\f[C]
+.EX
 # \[ti]/.gemstash/config.yml.erb
 ---
 :db_adapter: postgres
 :db_url: <%= ENV[\[dq]DATABASE_URL\[dq]] %>
-\f[R]
-.fi
+.EE

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

@@ -11,7 +11,7 @@
 
    1mSetup0m
        Several	customizable options are available via an interactive Gemstash
-       command.  Run 1mgemstash setup 22mand answer the questions  it  provides  (a
+       command.  Run gemstash setup and answer the questions  it  provides  (a
        blank answer will use the default value):
 
 	      $ gemstash setup
@@ -28,10 +28,10 @@
        Once you've answered the questions, some checks will be made to	ensure
        the configuration will work.  For example, the database didn't exist in
        the  previous  example,	so  the  command  failed and the configuration
-       wasn't saved.  If the command passes, you may provide the 1m--redo 22moption
+       wasn't saved.  If the command passes, you may provide the --redo option
        to force configuration to be redone:
 
-	      1m$ gemstash setup --redo0m
+	      $ gemstash setup --redo
 	      Where should files go?  [~/.gemstash]
 	      Cache with what?	[MEMORY, memcached] 1mmemcached0m
 	      What  is	the  comma  separated  Memcached   servers?    [local-
@@ -41,33 +41,33 @@
 	      Checking that the database is available
 	      You are all setup!
        Once  all  checks  have passed, Gemstash will store your answers in the
-       configuration file located at 1m~/.gemstash/config.yml22m.
+       configuration file located at ~/.gemstash/config.yml.
 
    1mFiles0m
-       Storage in Gemstash defaults to 1m~/.gemstash 22munless otherwise specified.
-       You can change this in your config file via the 1m:base_path 22mkey:
+       Storage in Gemstash defaults to ~/.gemstash unless otherwise specified.
+       You can change this in your config file via the :base_path key:
 
 	      # ~/.gemstash/config.yml
 	      ---
 	      :base_path: "/var/gemstash"
 
-       When customizing the 1mbase_path22m, the  directory  must  exist,  otherwise
-       Gemstash will fail to run.  Thus, if you want to use 1m/var/gemstash 22mlike
-       in the previous example, make sure to 1mmkdir /var/gemstash 22mand grant ac-
+       When customizing the base_path, the  directory  must  exist,  otherwise
+       Gemstash will fail to run.  Thus, if you want to use /var/gemstash like
+       in the previous example, make sure to mkdir /var/gemstash and grant ac-
        cess to the directory for the user you run Gemstash with.
 
    1mDatabase0m
-       The  1m:db_adapter  22mconfiguration key specifies what database you will be
-       using.  The default 1m:db_adapter 22mis	1msqlite3  22m(https://www.sqlite.org/),
-       which  will  use  a  database file located within your 1m:base_path22m.	The
-       database file will always be named 1mgemstash.db22m.
+       The  :db_adapter  configuration key specifies what database you will be
+       using.  The default :db_adapter is  sqlite3  (https://www.sqlite.org/),
+       which  will  use  a  database file located within your :base_path.  The
+       database file will always be named gemstash.db.
 
-       You  may  also	use   1mpostgres   22m(http://www.postgresql.org/),   1mmysql0m
-       (http://www.mysql.com/),      or     1mmysql2	 22m(http://sequel.jeremye-
+       You  may  also	use   postgres	 (http://www.postgresql.org/),	 mysql
+       (http://www.mysql.com/),      or     mysql2     (http://sequel.jeremye-
        vans.net/rdoc/files/doc/opening_databases_rdoc.html#label-mysql2)   for
-       your 1m:db_adapter22m.  When using any of these options, you need to specify
-       the  1m:db_url 22mto point to an existing database.  Here is an example con-
-       figuration to use the 1mpostgres 22madapter:
+       your :db_adapter.  When using any of these options, you need to specify
+       the  :db_url to point to an existing database.  Here is an example con-
+       figuration to use the postgres adapter:
 
 	      # ~/.gemstash/config.yml
 	      ---
@@ -81,7 +81,7 @@
        Regardless of the adapter you choose, the database  will  automatically
        migrate	to  your  version of Gemstash whenever the database is needed.
        You only need to ensure the database exists and Gemstash  will  do  the
-       rest, except for 1msqlite3 22m(for which Gemstash will also create the data-
+       rest, except for sqlite3 (for which Gemstash will also create the data-
        base for you).
 
    1mCache0m
@@ -93,15 +93,15 @@
 	      :cache_type: memory
 	      :cache_max_size: 2000
 
-       This configuration uses the default 1mmemory 22mcache, and has increased the
-       1mcache_max_size 22msetting from its default of 500 items.
+       This configuration uses the default memory cache, and has increased the
+       cache_max_size setting from its default of 500 items.
 
        The memory cache  can  optionally  be  swapped  out  with  a  Memcached
        (http://memcached.org/) server (or cluster of servers).
 
-       To use Memcached, use the 1mmemcached :cache_type 22mconfiguration.
+       To use Memcached, use the memcached :cache_type configuration.
 
-       Provide the servers as a comma-separated list to the 1m:memcached_servers0m
+       Provide the servers as a comma-separated list to the :memcached_servers
        configuration key:
 
 	      # ~/.gemstash/config.yml
@@ -110,7 +110,7 @@
 	      :memcached_servers: memcached1.local:11211,memcached2.local:11211
 	      :cache_expiration: 1800
 
-       All  caching expires in 1mcache_expiration 22mnumber of seconds.  Default is
+       All  caching expires in cache_expiration number of seconds.  Default is
        1800 seconds (30 minutes).  This option applies to all caching.
 
    1mServer0m
@@ -122,7 +122,7 @@
        ter/lib/gemstash/config.ru) for inspiration.
 
        While the server is not customizable, the way Gemstash binds  the  port
-       can  be changed.  To change the binding, update the 1m:bind 22mconfiguration
+       can  be changed.  To change the binding, update the :bind configuration
        key:
 
 	      # ~/.gemstash/config.yml
@@ -134,11 +134,11 @@
        anything valid for that flag.
 
        The  number  of	threads  Puma  uses  is  also  customizable  via   the
-       1m:puma_threads 22mconfiguration key.  The default is 1m1622m.
+       :puma_threads configuration key.  The default is 16.
 
    1mProtected Fetch0m
        Gemstash  by  default  allows  unauthenticated access for private gems.
-       Authenticated access is available via the  1m:protected_fetch  22mconfigura-
+       Authenticated access is available via the  :protected_fetch  configura-
        tion key.
 
 	      # ~/.gemstash/config.yml
@@ -148,15 +148,15 @@
        More details on protected_fetch are here.
 
    1mFetch Timeout0m
-       The  default  fetch timeout is 20 seconds.  Use the 1m:fetch_timeout 22mcon-
+       The  default  fetch timeout is 20 seconds.  Use the :fetch_timeout con-
        figuration key to change it.
 
 	      ---
 	      :fetch_timeout: 20
 
    1mConfig File Location0m
-       By default, configuration for  Gemstash	will  be  at  1m~/.gemstash/con-0m
-       1mfig.yml22m.   This can be changed by providing the 1m--config-file 22moption to
+       By default, configuration for  Gemstash	will  be  at  ~/.gemstash/con-
+       fig.yml.   This can be changed by providing the --config-file option to
        the various Gemstash commands:
 
 	      $ gemstash setup --config-file ./gemstash-config.yml
@@ -165,15 +165,15 @@
 	      $ gemstash stop --config-file ./gemstash-config.yml
 	      $ gemstash status --config-file ./gemstash-config.yml
 
-       When providing 1m--config-file 22mto 1mgemstash setup22m, the provided file  will
+       When providing --config-file to gemstash setup, the provided file  will
        be  output to with the provided configuration.  1mThis will overwrite 22many
        existing configuration.	If  the  file  doesn't	exist  when  providing
-       1m--config-file	22mto  1mgemstash  start22m, 1mgemstash stop22m, 1mgemstash status22m, and
-       1mgemstash authorize22m, the default configuration will be used.
+       --config-file  to  gemstash  start, gemstash stop, gemstash status, and
+       gemstash authorize, the default configuration will be used.
 
    1mERB parsed config0m
-       You may also create a  1m~/.gemstash/config.yml.erb  22mfile.   If  present,
-       this will be used instead of 1m~/.gemstash/config.yml22m.  For example, with
+       You may also create a  ~/.gemstash/config.yml.erb  file.   If  present,
+       this will be used instead of ~/.gemstash/config.yml.  For example, with
        this you can use environment variables in the config:
 
 	      # ~/.gemstash/config.yml.erb

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

@@ -1,46 +1,27 @@
 <!-- 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-debugging" "7" "October 28, 2015" "" ""
-.hy
 .SH Debugging Gemstash
-.PP
 If you are finding Gemstash isn\[cq]t behaving as you would expect, you
 might want to start by looking at the server log.
-You can find the log at \f[V]server.log\f[R] within your base directory.
-By default, this will be at \f[V]\[ti]/.gemstash/server.log\f[R].
+You can find the log at \f[CR]server.log\f[R] within your base
+directory.
+By default, this will be at \f[CR]\[ti]/.gemstash/server.log\f[R].
 .PP
 You might find it easier to view the log directly in your terminal.
 If you run Gemstash in non-daemonized form, the log will be output
 directly to standard out:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash start --no-daemonize
-\f[R]
-.fi
+.EE
 .PP
 You can also check the status of the server:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash status
-\f[R]
-.fi
+.EE
 .PP
 The server status is checked by passing through to
 pumactl (https://github.com/puma/puma#pumactl).

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

@@ -5,12 +5,12 @@
 1mDebugging Gemstash0m
        If  you	are  finding  Gemstash isn't behaving as you would expect, you
        might want to start by looking at the server log.  You can find the log
-       at 1mserver.log 22mwithin your base directory.  By default, this will be  at
-       1m~/.gemstash/server.log22m.
+       at server.log within your base directory.  By default, this will be  at
+       ~/.gemstash/server.log.
 
        You might find it easier to view the log directly in your terminal.  If
-       you run Gemstash in non-daemonized form, the log will be output direct-
-       ly to standard out:
+       you  run  Gemstash  in  non-daemonized form, the log will be output di-
+       rectly to standard out:
 
 	      $ gemstash start --no-daemonize
 
@@ -18,10 +18,10 @@
 
 	      $ gemstash status
 
-       The   server   status   is   checked  by  passing  through  to  pumactl
+       The  server  status  is	checked  by   passing	through   to   pumactl
        (https://github.com/puma/puma#pumactl).
 
-       If you find  a  bug,  please  don't  hesitate  to  open	a  bug	report
+       If  you	find  a  bug,  please  don't  hesitate	to  open  a bug report
        (https://github.com/rubygems/gemstash#contributing)!
 
 			       October 28, 2015 	 4mgemstash-debugging24m(7)

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

@@ -1,40 +1,22 @@
 <!-- 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-deploy" "7" "October 25, 2015" "" ""
-.hy
 .SH Deploying Gemstash
-.PP
 Bundler is here for the rescue to keep Gemstash up to date!
-Create a \f[V]Gemfile\f[R] pointing to Gemstash:
+Create a \f[CR]Gemfile\f[R] pointing to Gemstash:
 .IP
-.nf
-\f[C]
+.EX
 # ./Gemfile
 source \[dq]https://rubygems.org\[dq]
 gem \[dq]gemstash\[dq]
-\f[R]
-.fi
+.EE
 .PP
-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.
+Then \f[CR]bundle\f[R] to create your \f[CR]Gemfile.lock\f[R].
+When you are ready to upgrade, simply \f[CR]bundle update\f[R].
+You may need to run \f[CR]gemstash\f[R] via \f[CR]bundle exec\f[R].
+Alternatively, you can \f[CR]gem uninstall gemstash\f[R] and
+\f[CR]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.
@@ -42,25 +24,21 @@ the gem is all that needs to be done.
 It is probably wise to stop Gemstash before upgrading, then starting
 again once you are done:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle exec gemstash stop
 $ bundle update
 $ bundle exec gemstash start
-\f[R]
-.fi
+.EE
 .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)
 gem.
-If you request \f[V]/health\f[R] from your Gemstash instance, you will
+If you request \f[CR]/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:
 .IP
-.nf
-\f[C]
+.EX
 {
   \[dq]status\[dq]: {
     \[dq]heartbeat\[dq]: \[dq]OK\[dq],
@@ -70,18 +48,16 @@ The JSON response will look something like this for a success case:
     \[dq]db_write\[dq]: \[dq]OK\[dq]
   }
 }
-\f[R]
-.fi
+.EE
 .PP
 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\[cq]t interact
-with storage or the database, you can use \f[V]/health/heartbeat\f[R]
+with storage or the database, you can use \f[CR]/health/heartbeat\f[R]
 which will always respond with a success while your Gemstash server is
 running.
 .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.