gemstash 2.1.0 → 2.2.1

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

@@ -1,19 +1,34 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-customize" "7" "October 28, 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-customize" "7" "October 28, 2015" "" ""
 .hy
-.SH CUSTOMIZING THE SERVER
+.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
+.SS Setup
 .PP
 Several customizable options are available via an interactive Gemstash
 command.
-Run \f[C]gemstash setup\f[R] and answer the questions it provides (a
+Run \f[V]gemstash setup\f[R] and answer the questions it provides (a
 blank answer will use the default value):
 .RS
 .PP
@@ -64,11 +79,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[C]\-\-redo\f[R] option to
+If the command passes, you may provide the \f[V]--redo\f[R] option to
 force configuration to be redone:
 .RS
 .PP
-\f[C]$ gemstash setup \-\-redo\f[R]
+\f[V]$ gemstash setup --redo\f[R]
 .PD 0
 .P
 .PD
@@ -107,48 +122,48 @@ You are all setup!
 .RE
 .PP
 Once all checks have passed, Gemstash will store your answers in the
-configuration file located at \f[C]\[ti]/.gemstash/config.yml\f[R].
-.SS FILES
+configuration file located at \f[V]\[ti]/.gemstash/config.yml\f[R].
+.SS Files
 .PP
-Storage in Gemstash defaults to \f[C]\[ti]/.gemstash\f[R] unless
+Storage in Gemstash defaults to \f[V]\[ti]/.gemstash\f[R] unless
 otherwise specified.
-You can change this in your config file via the \f[C]:base_path\f[R]
+You can change this in your config file via the \f[V]:base_path\f[R]
 key:
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
+---
 :base_path: \[dq]/var/gemstash\[dq]
 \f[R]
 .fi
 .PP
-When customizing the \f[C]base_path\f[R], the directory must exist,
+When customizing the \f[V]base_path\f[R], the directory must exist,
 otherwise Gemstash will fail to run.
-Thus, if you want to use \f[C]/var/gemstash\f[R] like in the previous
-example, make sure to \f[C]mkdir /var/gemstash\f[R] and grant access to
+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
 the directory for the user you run Gemstash with.
-.SS DATABASE
+.SS Database
 .PP
-The \f[C]:db_adapter\f[R] configuration key specifies what database you
+The \f[V]:db_adapter\f[R] configuration key specifies what database you
 will be using.
-The default \f[C]:db_adapter\f[R] is
-\f[C]sqlite3\f[R] (https://www.sqlite.org/), which will use a database
-file located within your \f[C]:base_path\f[R].
-The database file will always be named \f[C]gemstash.db\f[R].
+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].
 .PP
-You may also use \f[C]postgres\f[R] (http://www.postgresql.org/),
-\f[C]mysql\f[R] (http://www.mysql.com/), or
-\f[C]mysql2\f[R] (http://sequel.jeremyevans.net/rdoc/files/doc/opening_databases_rdoc.html#label-mysql2)
-for your \f[C]:db_adapter\f[R].
+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].
 When using any of these options, you need to specify the
-\f[C]:db_url\f[R] to point to an existing database.
-Here is an example configuration to use the \f[C]postgres\f[R] adapter:
+\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:
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
+---
 :db_adapter: postgres
 :db_url: postgres:///gemstash
 :db_connection_options: # Sequel.connect options
@@ -161,9 +176,9 @@ Here is an example configuration to use the \f[C]postgres\f[R] adapter:
 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[C]sqlite3\f[R] (for which Gemstash will also create
+rest, except for \f[V]sqlite3\f[R] (for which Gemstash will also create
 the database for you).
-.SS CACHE
+.SS Cache
 .PP
 Certain things (like dependencies) are cached in memory.
 This avoids web calls to the gem source, and database calls for private
@@ -172,39 +187,39 @@ gems.
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
+---
 :cache_type: memory
 :cache_max_size: 2000
 \f[R]
 .fi
 .PP
-This configuration uses the default \f[C]memory\f[R] cache, and has
-increased the \f[C]cache_max_size\f[R] setting from its default of 500
+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
 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[C]memcached\f[R] \f[C]:cache_type\f[R]
+To use Memcached, use the \f[V]memcached\f[R] \f[V]:cache_type\f[R]
 configuration.
 .PP
-Provide the servers as a comma\-separated list to the
-\f[C]:memcached_servers\f[R] configuration key:
+Provide the servers as a comma-separated list to the
+\f[V]:memcached_servers\f[R] configuration key:
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
+---
 :cache_type: memcached
 :memcached_servers: memcached1.local:11211,memcached2.local:11211
 :cache_expiration: 1800
 \f[R]
 .fi
 .PP
-All caching expires in \f[C]cache_expiration\f[R] number of seconds.
+All caching expires in \f[V]cache_expiration\f[R] number of seconds.
 Default is 1800 seconds (30 minutes).
 This option applies to all caching.
-.SS SERVER
+.SS Server
 .PP
 Gemstash uses Puma (http://puma.io/) and Rack (http://rack.github.io/)
 as the server.
@@ -217,12 +232,12 @@ 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[C]:bind\f[R] configuration key:
+To change the binding, update the \f[V]:bind\f[R] configuration key:
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
+---
 :bind: tcp://0.0.0.0:4242
 \f[R]
 .fi
@@ -232,69 +247,69 @@ 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[C]:puma_threads\f[R] configuration key.
-The default is \f[C]16\f[R].
-.SS PROTECTED FETCH
+\f[V]:puma_threads\f[R] configuration key.
+The default is \f[V]16\f[R].
+.SS Protected Fetch
 .PP
 Gemstash by default allows unauthenticated access for private gems.
-Authenticated access is available via the \f[C]:protected_fetch\f[R]
+Authenticated access is available via the \f[V]:protected_fetch\f[R]
 configuration key.
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml
-\-\-\-
+---
 :protected_fetch: true
 \f[R]
 .fi
 .PP
-More details on protected_fetch are here (gemstash help private-gems.7).
-.SS FETCH TIMEOUT
+More details on protected_fetch are here.
+.SS Fetch Timeout
 .PP
 The default fetch timeout is 20 seconds.
-Use the \f[C]:fetch_timeout\f[R] configuration key to change it.
+Use the \f[V]:fetch_timeout\f[R] configuration key to change it.
 .IP
 .nf
 \f[C]
-\-\-\-
+---
 :fetch_timeout: 20
 \f[R]
 .fi
-.SS CONFIG FILE LOCATION
+.SS Config File Location
 .PP
 By default, configuration for Gemstash will be at
-\f[C]\[ti]/.gemstash/config.yml\f[R].
-This can be changed by providing the \f[C]\-\-config\-file\f[R] option
-to the various Gemstash commands:
+\f[V]\[ti]/.gemstash/config.yml\f[R].
+This can be changed by providing the \f[V]--config-file\f[R] option to
+the various Gemstash commands:
 .IP
 .nf
 \f[C]
-$ 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
+$ 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
 .PP
-When providing \f[C]\-\-config\-file\f[R] to \f[C]gemstash setup\f[R],
-the provided file will be output to with the provided configuration.
+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.
 \f[B]This will overwrite\f[R] any existing configuration.
-If the file doesn\[cq]t exist when providing \f[C]\-\-config\-file\f[R]
-to \f[C]gemstash start\f[R], \f[C]gemstash stop\f[R],
-\f[C]gemstash status\f[R], and \f[C]gemstash authorize\f[R], the default
+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.
-.SS ERB PARSED CONFIG
+.SS ERB parsed config
 .PP
-You may also create a \f[C]\[ti]/.gemstash/config.yml.erb\f[R] file.
+You may also create a \f[V]\[ti]/.gemstash/config.yml.erb\f[R] file.
 If present, this will be used instead of
-\f[C]\[ti]/.gemstash/config.yml\f[R].
+\f[V]\[ti]/.gemstash/config.yml\f[R].
 For example, with this you can use environment variables in the config:
 .IP
 .nf
 \f[C]
 # \[ti]/.gemstash/config.yml.erb
-\-\-\-
+---
 :db_adapter: postgres
 :db_url: <%= ENV[\[dq]DATABASE_URL\[dq]] %>
 \f[R]

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

@@ -2,22 +2,24 @@ gemstash-customize(7)					 gemstash-customize(7)
 
 
 
-1mCUSTOMIZING THE SERVER0m
-       Although	 Gemstash  is designed for as minimal setup as possible, there
+<!-- Automatically generated by Pandoc -->
+
+1mCustomizing the Server0m
+       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
+       By  the	end  of  this guide, you will be able to customize some of the
        Gemstash behavior, including where files are stored, what database Gem-
        stash uses, and how Gemstash caches certain requests.
 
-   1mSETUP0m
+   1mSetup0m
        Several	customizable options are available via an interactive Gemstash
-       command.	 Run gemstash setup and answer the questions  it  provides  (a
+       command.  Run 1mgemstash setup 22mand answer the questions  it  provides  (a
        blank answer will use the default value):
 
 	      $ gemstash setup
 	      Where should files go?  [~/.gemstash]
 	      Cache with what?	[MEMORY, memcached] 1mmemcached0m
-	      What   is	  the  comma  separated	 Memcached  servers?   [local-
+	      What   is   the  comma  separated  Memcached  servers?   [local-
 	      host:11211]
 	      What database adapter?  [SQLITE3, postgres, mysql, mysql2] 1mpost-0m
 	      1mgres0m
@@ -27,47 +29,47 @@ gemstash-customize(7)					 gemstash-customize(7)
 	      The database is not available
        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 --redo option
+       the  previous  example,	so  the  command  failed and the configuration
+       wasn't saved.  If the command passes, you may provide the 1m--redo 22moption
        to force configuration to be redone:
 
-	      $ gemstash setup --redo
+	      1m$ gemstash setup --redo0m
 	      Where should files go?  [~/.gemstash]
 	      Cache with what?	[MEMORY, memcached] 1mmemcached0m
-	      What   is	  the  comma  separated	 Memcached  servers?   [local-
+	      What   is   the  comma  separated  Memcached  servers?   [local-
 	      host:11211]
 	      What database adapter?  [SQLITE3, postgres, mysql, mysql2]
 	      Checking that the cache is available
 	      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 ~/.gemstash/config.yml.
+       configuration file located at 1m~/.gemstash/config.yml22m.
 
-   1mFILES0m
-       Storage in Gemstash defaults to ~/.gemstash unless otherwise specified.
-       You can change this in your config file via the :base_path key:
+   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:
 
 	      # ~/.gemstash/config.yml
 	      ---
 	      :base_path: "/var/gemstash"
 
-       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-
+       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-
        cess to the directory for the user you run Gemstash with.
 
-   1mDATABASE0m
-       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.
+   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.
 
-       You  may	 also	use   postgres	 (http://www.postgresql.org/),	 mysql
-       (http://www.mysql.com/),	     or	    mysql2     (http://sequel.jeremye-
+       You  may  also	use   1mpostgres   22m(http://www.postgresql.org/),   1mmysql0m
+       (http://www.mysql.com/),      or     1mmysql2	 22m(http://sequel.jeremye-
        vans.net/rdoc/files/doc/opening_databases_rdoc.html#label-mysql2)   for
-       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:
+       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:
 
 	      # ~/.gemstash/config.yml
 	      ---
@@ -79,12 +81,12 @@ gemstash-customize(7)					 gemstash-customize(7)
 		:timeout: 30
 
        Regardless  of  the adapter you choose, the database will automatically
-       migrate to your version of Gemstash whenever the	 database  is  needed.
+       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 sqlite3 (for which Gemstash will also create the data-
+       rest, except for 1msqlite3 22m(for which Gemstash will also create the data-
        base for you).
 
-   1mCACHE0m
+   1mCache0m
        Certain	things	(like dependencies) are cached in memory.  This avoids
        web calls to the gem source, and database calls for private gems.
 
@@ -93,15 +95,15 @@ gemstash-customize(7)					 gemstash-customize(7)
 	      :cache_type: memory
 	      :cache_max_size: 2000
 
-       This configuration uses the default memory cache, and has increased the
-       cache_max_size setting from its default of 500 items.
+       This configuration uses the default 1mmemory 22mcache, and has increased the
+       1mcache_max_size 22msetting from its default of 500 items.
 
-       The  memory  cache  can	optionally  be	swapped	 out  with a Memcached
+       The  memory  cache  can	optionally  be	swapped  out  with a Memcached
        (http://memcached.org/) server (or cluster of servers).
 
-       To use Memcached, use the memcached :cache_type configuration.
+       To use Memcached, use the 1mmemcached :cache_type 22mconfiguration.
 
-       Provide the servers as a comma-separated list to the :memcached_servers
+       Provide the servers as a comma-separated list to the 1m:memcached_servers0m
        configuration key:
 
 	      # ~/.gemstash/config.yml
@@ -110,19 +112,19 @@ gemstash-customize(7)					 gemstash-customize(7)
 	      :memcached_servers: memcached1.local:11211,memcached2.local:11211
 	      :cache_expiration: 1800
 
-       All  caching expires in cache_expiration number of seconds.  Default is
+       All  caching expires in 1mcache_expiration 22mnumber of seconds.  Default is
        1800 seconds (30 minutes).  This option applies to all caching.
 
-   1mSERVER0m
+   1mServer0m
        Gemstash uses Puma (http://puma.io/) and Rack  (http://rack.github.io/)
        as  the server.	Alternate server configurations are not currently sup-
-       ported,	but  you  can  take  a	look   at   the	  Puma	 configuration
+       ported,	but  you  can  take  a	look   at   the   Puma	 configuration
        (https://github.com/rubygems/gemstash/blob/master/lib/gemstash/puma.rb)
-       and  the	 rackup	 file  (https://github.com/rubygems/gemstash/blob/mas-
+       and  the  rackup  file  (https://github.com/rubygems/gemstash/blob/mas-
        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 :bind	 configuration
+       can be changed.	To change the binding, update the 1m:bind  22mconfiguration
        key:
 
 	      # ~/.gemstash/config.yml
@@ -130,34 +132,33 @@ gemstash-customize(7)					 gemstash-customize(7)
 	      :bind: tcp://0.0.0.0:4242
 
        This	 maps	   directly	 to	the	Puma	 bind	  flag
-       (https://github.com/puma/puma#binding-tcp--sockets), and	 will  support
+       (https://github.com/puma/puma#binding-tcp--sockets), and  will  support
        anything valid for that flag.
 
-       The   number  of	 threads  Puma	uses  is  also	customizable  via  the
-       :puma_threads configuration key.	 The default is 16.
+       The   number  of  threads  Puma	uses  is  also	customizable  via  the
+       1m:puma_threads 22mconfiguration key.  The default is 1m1622m.
 
-   1mPROTECTED FETCH0m
-       Gemstash by default allows unauthenticated  access  for	private	 gems.
-       Authenticated  access  is available via the :protected_fetch configura-
+   1mProtected Fetch0m
+       Gemstash by default allows unauthenticated  access  for	private  gems.
+       Authenticated  access  is available via the 1m:protected_fetch 22mconfigura-
        tion key.
 
 	      # ~/.gemstash/config.yml
 	      ---
 	      :protected_fetch: true
 
-       More details  on	 protected_fetch  are  here  (gemstash	help  private-
-       gems.7).
+       More details on protected_fetch are here.
 
-   1mFETCH TIMEOUT0m
-       The  default  fetch timeout is 20 seconds.  Use the :fetch_timeout con-
+   1mFetch Timeout0m
+       The default fetch timeout is 20 seconds.  Use the  1m:fetch_timeout  22mcon-
        figuration key to change it.
 
 	      ---
 	      :fetch_timeout: 20
 
-   1mCONFIG FILE LOCATION0m
-       By default, configuration for  Gemstash	will  be  at  ~/.gemstash/con-
-       fig.yml.	  This can be changed by providing the --config-file option to
+   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
        the various Gemstash commands:
 
 	      $ gemstash setup --config-file ./gemstash-config.yml
@@ -166,15 +167,15 @@ gemstash-customize(7)					 gemstash-customize(7)
 	      $ gemstash stop --config-file ./gemstash-config.yml
 	      $ gemstash status --config-file ./gemstash-config.yml
 
-       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
-       --config-file  to  gemstash  start, gemstash stop, gemstash status, and
-       gemstash authorize, the default configuration will be used.
+       When  providing 1m--config-file 22mto 1mgemstash setup22m, 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.
 
-   1mERB PARSED CONFIG0m
-       You may also create a  ~/.gemstash/config.yml.erb  file.	  If  present,
-       this will be used instead of ~/.gemstash/config.yml.  For example, with
+   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
        this you can use environment variables in the config:
 
 	      # ~/.gemstash/config.yml.erb
@@ -184,4 +185,4 @@ gemstash-customize(7)					 gemstash-customize(7)
 
 
 
-			       October 28, 2015		 gemstash-customize(7)
+			       October 28, 2015 	 gemstash-customize(7)

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

@@ -1,25 +1,40 @@
-.\" Automatically generated by Pandoc 2.5
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.0.1
 .\"
-.TH "gemstash\-debugging" "7" "October 28, 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-debugging" "7" "October 28, 2015" "" ""
 .hy
-.SH DEBUGGING GEMSTASH
+.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[C]server.log\f[R] within your base directory.
-By default, this will be at \f[C]\[ti]/.gemstash/server.log\f[R].
+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].
 .PP
 You might find it easier to view the log directly in your terminal.
-If you run Gemstash in non\-daemonized form (gemstash help start.1), the
-log will be output directly to standard out:
+If you run Gemstash in non-daemonized form, the log will be output
+directly to standard out:
 .IP
 .nf
 \f[C]
-$ gemstash start \-\-no\-daemonize
+$ gemstash start --no-daemonize
 \f[R]
 .fi
 .PP
-You can also check the status (gemstash help status.1) of the server:
+You can also check the status of the server:
 .IP
 .nf
 \f[C]

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

@@ -2,28 +2,30 @@ gemstash-debugging(7)					 gemstash-debugging(7)
 
 
 
-1mDEBUGGING GEMSTASH0m
+<!-- Automatically generated by Pandoc -->
+
+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  server.log within your base directory.  By default, this will be at
-       ~/.gemstash/server.log.
+       at  1mserver.log 22mwithin your base directory.	By default, this will be at
+       1m~/.gemstash/server.log22m.
 
        You might find it easier to view the log directly in your terminal.  If
-       you  run	 Gemstash  in non-daemonized form (gemstash help start.1), the
-       log will be output directly to standard out:
+       you run Gemstash in non-daemonized form, the log will be output direct-
+       ly to standard out:
 
 	      $ gemstash start --no-daemonize
 
-       You can also check the status (gemstash help status.1) of the server:
+       You can also check the status of the server:
 
 	      $ 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		 gemstash-debugging(7)
+			       October 28, 2015 	 gemstash-debugging(7)