gemstash 2.2.2 → 2.7.1

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

@@ -1,29 +1,13 @@
 <!-- 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-readme" "7" "November 30, 2015" "" ""
-.hy
 .SH Gemstash
 .SS What is Gemstash?
-.PP
 Gemstash is both a cache for remote servers such as
 https://rubygems.org, and a private gem source.
 .PP
-If you are using bundler (http://bundler.io/) across many machines that
+If you are using bundler (https://bundler.io/) across many machines that
 have access to a server within your control, you might want to use
 Gemstash.
 .PP
@@ -38,16 +22,15 @@ the same gems frequently?
 Well, maybe you don\[cq]t need Gemstash\&...
 yet.
 .PP
-Gemstash is maintained by Ruby Together (https://rubytogether.org/), a
-grassroots initiative committed to supporting the critical Ruby
-infrastructure you rely on.
-Contribute today as an individual (https://rubytogether.org/developers)
-or even better, as a company (https://rubytogether.org/companies), and
-ensure that Bundler, RubyGems, Gemstash, and other shared tooling is
-around for years to come.
+Gemstash is maintained by Ruby Central (https://rubycentral.org/), a
+non-profit committed to supporting the critical Ruby infrastructure you
+rely on.
+Contribute today as an individual, or even better, as a
+company (https://rubycentral.org/#/portal/signup), and ensure that
+Bundler, RubyGems, Gemstash, and other shared tooling is around for
+years to come.
 .SS Quickstart Guide
 .SS Setup
-.PP
 Gemstash is designed to be quick and painless to get set up.
 By the end of this Quickstart Guide, you will be able to bundle stashed
 gems from public sources against a Gemstash server running on your
@@ -55,56 +38,45 @@ machine.
 .PP
 Install Gemstash to get started:
 .IP
-.nf
-\f[C]
+.EX
 $ gem install gemstash
-\f[R]
-.fi
+.EE
 .PP
 After it is installed, starting Gemstash requires no additional steps.
-Simply start the Gemstash server with the \f[V]gemstash\f[R] command:
+Simply start the Gemstash server with the \f[CR]gemstash\f[R] command:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash start
-\f[R]
-.fi
+.EE
 .PP
 You may have noticed that the command finished quickly.
 This is because Gemstash will run the server in the background by
 default.
 The server runs on port 9292.
 .SS Bundling
-.PP
 With the server running, you can bundle against it.
 Tell Bundler that you want to use Gemstash to find gems from
 RubyGems.org:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config mirror.https://rubygems.org http://localhost:9292
-\f[R]
-.fi
+.EE
 .PP
 Now you can create a Gemfile and install gems through Gemstash:
 .IP
-.nf
-\f[C]
+.EX
 # ./Gemfile
 source \[dq]https://rubygems.org\[dq]
 gem \[dq]rubywarrior\[dq]
-\f[R]
-.fi
+.EE
 .PP
 The gems you include should be gems you don\[cq]t yet have installed,
 otherwise Gemstash will have nothing to stash.
 Now bundle:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle install --path .bundle
-\f[R]
-.fi
+.EE
 .PP
 Your Gemstash server has fetched the gems from https://rubygems.org and
 cached them for you!
@@ -114,65 +86,52 @@ Gem dependencies metadata are cached for 30 minutes, so if you bundle
 again before that, you can successfully bundle without an Internet
 connection:
 .IP
-.nf
-\f[C]
+.EX
 $ # Disable your Internet first!
 $ rm -rf Gemfile.lock .bundle
 $ bundle
-\f[R]
-.fi
+.EE
 .SS Falling back to rubygems.org
-.PP
 If you want to make sure that your bundling from https://rubygems.org
 still works as expected when the Gemstash server is not running, you can
 easily configure Bundler to fallback to https://rubygems.org.
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config mirror.https://rubygems.org.fallback_timeout true
-\f[R]
-.fi
+.EE
 .PP
 You can also configure this fallback as a number of seconds in case the
 Gemstash server is simply unresponsive.
 This example uses a 3 second timeout:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config mirror.https://rubygems.org.fallback_timeout 3
-\f[R]
-.fi
+.EE
 .SS Stopping the Server
-.PP
 Once you\[cq]ve finish using your Gemstash server, you can stop it just
 as easily as you started it:
 .IP
-.nf
-\f[C]
+.EX
 $ gemstash stop
-\f[R]
-.fi
+.EE
 .PP
 You\[cq]ll also want to tell Bundler that it can go back to getting gems
 from RubyGems.org directly, instead of going through Gemstash:
 .IP
-.nf
-\f[C]
+.EX
 $ bundle config --delete mirror.https://rubygems.org
-\f[R]
-.fi
+.EE
 .SS Under the Hood
-.PP
 You might wonder where the gems are stored.
 After running the commands above, you will find a new directory at
-\f[V]\[ti]/.gemstash\f[R].
+\f[CR]\[ti]/.gemstash\f[R].
 This directory holds all the cached and private gems.
 It also has a server log, the database, and configuration for Gemstash.
 If you prefer, you can point to a different directory.
 .PP
 Gemstash uses SQLite (https://www.sqlite.org/) to store details about
 private gems.
-The database will be located in \f[V]\[ti]/.gemstash\f[R], however you
+The database will be located in \f[CR]\[ti]/.gemstash\f[R], however you
 won\[cq]t see the database appear until you start using private gems.
 If you prefer, you can use a different database.
 .PP
@@ -181,14 +140,13 @@ Anything cached in memory will last for 30 minutes before being
 retrieved again.
 You can use memcached instead of caching in memory.
 Gem files are always cached permanently, so bundling with a
-\f[V]Gemfile.lock\f[R] with all gems cached will never call out to
+\f[CR]Gemfile.lock\f[R] with all gems cached will never call out to
 https://rubygems.org.
 .PP
-The server you ran is provided via Puma (http://puma.io/) and
-Rack (http://rack.github.io/), however they are not customizable at this
-point.
+The server you ran is provided via Puma (https://puma.io/) and
+Rack (https://github.com/rack/rack), however they are not customizable
+at this point.
 .SS Deep Dive
-.PP
 Deep dive into more subjects:
 .IP \[bu] 2
 Private gems
@@ -203,7 +161,6 @@ Deploying Gemstash
 .IP \[bu] 2
 Debugging Gemstash
 .SS Reference
-.PP
 An anatomy of various configuration and commands:
 .IP \[bu] 2
 Configuration
@@ -221,25 +178,22 @@ Setup
 Version
 .PP
 To see what has changed in recent versions of Gemstash, see the
-CHANGELOG (https://github.com/rubygems/gemstash/blob/master/CHANGELOG.md).
+CHANGELOG (https://github.com/rubygems/gemstash/blob/main/CHANGELOG.md).
 .SS Development
-.PP
-After checking out the repo, run \f[V]bin/setup\f[R] to install
+After checking out the repo, run \f[CR]bin/setup\f[R] to install
 dependencies.
-Then, run \f[V]rake\f[R] to run RuboCop and the tests.
-While developing, you can run \f[V]bin/gemstash\f[R] to run Gemstash.
-You can also run \f[V]bin/console\f[R] for an interactive prompt that
+Then, run \f[CR]rake\f[R] to run RuboCop and the tests.
+While developing, you can run \f[CR]bin/gemstash\f[R] to run Gemstash.
+You can also run \f[CR]bin/console\f[R] for an interactive prompt that
 will allow you to experiment.
 .SS Contributing
-.PP
 Bug reports and pull requests are welcome on GitHub at
 https://github.com/rubygems/gemstash.
 This project is intended to be a safe, welcoming space for
 collaboration, and contributors are expected to adhere to the
 Contributor
-Covenant (https://github.com/rubygems/gemstash/blob/master/CODE_OF_CONDUCT.md)
+Covenant (https://github.com/rubygems/gemstash/blob/main/CODE_OF_CONDUCT.md)
 code of conduct.
 .SS License
-.PP
 The gem is available as open source under the terms of the MIT
 License (http://opensource.org/licenses/MIT).

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

@@ -1,6 +1,4 @@
-gemstash-readme(7)					    gemstash-readme(7)
-
-
+4mgemstash-readme24m(7) 					 4mgemstash-readme24m(7)
 
 <!-- Automatically generated by Pandoc -->
 
@@ -9,11 +7,11 @@ gemstash-readme(7)					    gemstash-readme(7)
        Gemstash    is	 both	a   cache   for   remote   servers   such   as
        https://rubygems.org, and a private gem source.
 
-       If you are using bundler (http://bundler.io/) across many machines that
-       have access to a server within your control, you might want to use Gem-
-       stash.
+       If you are using bundler  (https://bundler.io/)	across	many  machines
+       that have access to a server within your control, you might want to use
+       Gemstash.
 
-       If you produce gems that you don't want everyone in the world  to  have
+       If  you	produce gems that you don't want everyone in the world to have
        access to, you might want to use Gemstash.
 
        If you frequently bundle the same set of gems across multiple projects,
@@ -22,35 +20,34 @@ gemstash-readme(7)					    gemstash-readme(7)
        Are you only using gems from https://rubygems.org, and don't bundle the
        same gems frequently?  Well, maybe you don't need Gemstash...  yet.
 
-       Gemstash  is maintained by Ruby Together (https://rubytogether.org/), a
-       grassroots initiative committed to supporting the critical Ruby	infra-
-       structure   you	 rely	on.    Contribute   today   as	an  individual
-       (https://rubytogether.org/developers) or  even  better,	as  a  company
-       (https://rubytogether.org/companies),	and   ensure   that   Bundler,
-       RubyGems, Gemstash, and other shared tooling is	around	for  years  to
-       come.
+       Gemstash is maintained by Ruby  Central	(https://rubycentral.org/),  a
+       non-profit committed to supporting the critical Ruby infrastructure you
+       rely  on.  Contribute today as an individual, or even better, as a com-
+       pany   (https://rubycentral.org/#/portal/signup),   and	 ensure   that
+       Bundler,  RubyGems,  Gemstash,  and  other shared tooling is around for
+       years to come.
 
    1mQuickstart Guide0m
    1mSetup0m
-       Gemstash  is  designed  to be quick and painless to get set up.	By the
-       end of this Quickstart Guide, you will be able to bundle  stashed  gems
+       Gemstash is designed to be quick and painless to get set  up.   By  the
+       end  of	this Quickstart Guide, you will be able to bundle stashed gems
        from public sources against a Gemstash server running on your machine.
 
        Install Gemstash to get started:
 
 	      $ gem install gemstash
 
-       After  it is installed, starting Gemstash requires no additional steps.
-       Simply start the Gemstash server with the 1mgemstash 22mcommand:
+       After it is installed, starting Gemstash requires no additional	steps.
+       Simply start the Gemstash server with the gemstash command:
 
 	      $ gemstash start
 
-       You may have noticed that the command finished quickly.	 This  is  be-
-       cause  Gemstash	will run the server in the background by default.  The
+       You  may  have  noticed that the command finished quickly.  This is be-
+       cause Gemstash will run the server in the background by	default.   The
        server runs on port 9292.
 
    1mBundling0m
-       With the server running, you can bundle against it.  Tell Bundler  that
+       With  the server running, you can bundle against it.  Tell Bundler that
        you want to use Gemstash to find gems from RubyGems.org:
 
 	      $ bundle config mirror.https://rubygems.org http://localhost:9292
@@ -61,7 +58,7 @@ gemstash-readme(7)					    gemstash-readme(7)
 	      source "https://rubygems.org"
 	      gem "rubywarrior"
 
-       The  gems you include should be gems you don't yet have installed, oth-
+       The gems you include should be gems you don't yet have installed,  oth-
        erwise Gemstash will have nothing to stash.  Now bundle:
 
 	      $ bundle install --path .bundle
@@ -70,7 +67,7 @@ gemstash-readme(7)					    gemstash-readme(7)
        cached them for you!  To prove this, you can disable your Internet con-
        nection and try again.  Gem files (*.gem) are cached indefinitely.  Gem
        dependencies metadata are cached for 30 minutes, so if you bundle again
-       before that, you can successfully bundle without  an  Internet  connec-
+       before  that,  you  can successfully bundle without an Internet connec-
        tion:
 
 	      $ # Disable your Internet first!
@@ -78,8 +75,8 @@ gemstash-readme(7)					    gemstash-readme(7)
 	      $ bundle
 
    1mFalling back to rubygems.org0m
-       If  you	want to make sure that your bundling from https://rubygems.org
-       still works as expected when the Gemstash server is  not  running,  you
+       If you want to make sure that your bundling  from  https://rubygems.org
+       still  works  as  expected when the Gemstash server is not running, you
        can easily configure Bundler to fallback to https://rubygems.org.
 
 	      $ bundle config mirror.https://rubygems.org.fallback_timeout true
@@ -103,26 +100,26 @@ gemstash-readme(7)					    gemstash-readme(7)
 
    1mUnder the Hood0m
        You might wonder where the gems are stored.  After running the commands
-       above, you will find a new directory at	1m~/.gemstash22m.   This  directory
-       holds  all  the cached and private gems.  It also has a server log, the
+       above,  you  will  find a new directory at ~/.gemstash.	This directory
+       holds all the cached and private gems.  It also has a server  log,  the
        database, and configuration for Gemstash.  If you prefer, you can point
        to a different directory.
 
        Gemstash  uses  SQLite (https://www.sqlite.org/) to store details about
-       private gems.  The database will be located in 1m~/.gemstash22m, however you
-       won't  see  the database appear until you start using private gems.  If
+       private gems.  The database will be located in ~/.gemstash, however you
+       won't see the database appear until you start using private  gems.   If
        you prefer, you can use a different database.
 
-       Gemstash temporarily caches things like	gem  dependencies  in  memory.
-       Anything  cached  in  memory  will last for 30 minutes before being re-
-       trieved again.  You can use memcached instead  of  caching  in  memory.
-       Gem  files  are	always	cached	permanently,  so  bundling with a 1mGem-0m
-       1mfile.lock   22mwith   all   gems   cached   will   never   call   out	 to
+       Gemstash  temporarily  caches  things  like gem dependencies in memory.
+       Anything cached in memory will last for 30  minutes  before  being  re-
+       trieved	again.	 You  can  use memcached instead of caching in memory.
+       Gem files are always  cached  permanently,  so  bundling  with  a  Gem-
+       file.lock   with   all	gems   cached	will   never   call   out   to
        https://rubygems.org.
 
-       The  server  you  ran  is  provided via Puma (http://puma.io/) and Rack
-       (http://rack.github.io/), however they are  not	customizable  at  this
-       point.
+       The server you ran is provided via  Puma  (https://puma.io/)  and  Rack
+       (https://github.com/rack/rack),	however  they  are not customizable at
+       this point.
 
    1mDeep Dive0m
        Deep dive into more subjects:
@@ -156,27 +153,25 @@ gemstash-readme(7)					    gemstash-readme(7)
 
        o Version
 
-       To  see	what  has  changed  in	recent	versions  of Gemstash, see the
-       CHANGELOG    (https://github.com/rubygems/gemstash/blob/master/CHANGEL-
-       OG.md).
+       To see what has	changed  in  recent  versions  of  Gemstash,  see  the
+       CHANGELOG			     (https://github.com/rubygems/gem-
+       stash/blob/main/CHANGELOG.md).
 
    1mDevelopment0m
-       After  checking	out  the  repo, run 1mbin/setup 22mto install dependencies.
-       Then, run 1mrake 22mto run RuboCop and the tests.  While developing, you can
-       run  1mbin/gemstash 22mto run Gemstash.	You can also run 1mbin/console 22mfor an
+       After checking out the repo, run  bin/setup  to	install  dependencies.
+       Then, run rake to run RuboCop and the tests.  While developing, you can
+       run  bin/gemstash to run Gemstash.  You can also run bin/console for an
        interactive prompt that will allow you to experiment.
 
    1mContributing0m
        Bug  reports   and   pull   requests   are   welcome   on   GitHub   at
        https://github.com/rubygems/gemstash.  This project is intended to be a
-       safe, welcoming space for collaboration, and contributors are  expected
+       safe,  welcoming space for collaboration, and contributors are expected
        to adhere to the Contributor Covenant (https://github.com/rubygems/gem-
-       stash/blob/master/CODE_OF_CONDUCT.md) code of conduct.
+       stash/blob/main/CODE_OF_CONDUCT.md) code of conduct.
 
    1mLicense0m
        The gem is available as open source under the terms of the MIT  License
        (http://opensource.org/licenses/MIT).
 
-
-
-			       November 30, 2015	    gemstash-readme(7)
+			       November 30, 2015	    4mgemstash-readme24m(7)

data/lib/gemstash/man/gemstash-setup.1

@@ -1,58 +1,38 @@
 <!-- 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-setup" "1" "October 9, 2015" "" ""
-.hy
 .SH Name
-.PP
 gemstash-setup - Customize your Gemstash configuration interactively
 .SH Synopsis
-.PP
-\f[V]gemstash setup [--redo] [--debug] [--config-file FILE]\f[R]
+\f[CR]gemstash setup [--redo] [--debug] [--config-file FILE]\f[R]
 .SH Description
-.PP
 Customize your Gemstash configuration interactively.
 This will save your config file, but only if a few checks pass after
 you\[cq]ve provided your answers.
 .SS Usage
 .IP
-.nf
-\f[C]
+.EX
 gemstash setup
 gemstash setup --redo
 gemstash setup --config-file <file>
-\f[R]
-.fi
+.EE
 .SH Options
 .IP \[bu] 2
-\f[V]--redo\f[R]: Redo the configuration.
-This does nothing the first time \f[V]gemstash setup\f[R] is run.
-If you want to change your configuration using \f[V]gemstash setup\f[R]
+\f[CR]--redo\f[R]: Redo the configuration.
+This does nothing the first time \f[CR]gemstash setup\f[R] is run.
+If you want to change your configuration using \f[CR]gemstash setup\f[R]
 after you\[cq]ve run it before, you must provide this option, otherwise
 Gemstash will simply indicate your setup is complete.
 .IP \[bu] 2
-\f[V]--debug\f[R]: Output additional information if one of the checks at
-the end of setup fails.
+\f[CR]--debug\f[R]: Output additional information if one of the checks
+at the end of setup fails.
 This will do nothing if all checks pass.
 .IP \[bu] 2
-\f[V]--config-file FILE\f[R]: Specify the config file to write to.
+\f[CR]--config-file FILE\f[R]: Specify the config file to write to.
 Without this option, your configuration will be written to
-\f[V]\[ti]/.gemstash/config.yml\f[R].
+\f[CR]\[ti]/.gemstash/config.yml\f[R].
 If you write to a custom location, you will need to pass the
-\f[V]--config-file\f[R] option to all Gemstash commands.
+\f[CR]--config-file\f[R] option to all Gemstash commands.
 If you plan to use ERB in your config file, you might want to use
-\f[V]\[ti]/.gemstash/config.yml.erb\f[R].
+\f[CR]\[ti]/.gemstash/config.yml.erb\f[R].

data/lib/gemstash/man/gemstash-setup.1.txt

@@ -1,6 +1,4 @@
-gemstash-setup(1)					     gemstash-setup(1)
-
-
+4mgemstash-setup24m(1)						  4mgemstash-setup24m(1)
 
 <!-- Automatically generated by Pandoc -->
 
@@ -8,7 +6,7 @@ gemstash-setup(1)					     gemstash-setup(1)
        gemstash-setup - Customize your Gemstash configuration interactively
 
 1mSynopsis0m
-       1mgemstash setup [--redo] [--debug] [--config-file FILE]0m
+       gemstash setup [--redo] [--debug] [--config-file FILE]
 
 1mDescription0m
        Customize  your	Gemstash  configuration interactively.	This will save
@@ -21,22 +19,20 @@ gemstash-setup(1)					     gemstash-setup(1)
 	      gemstash setup --config-file <file>
 
 1mOptions0m
-       o 1m--redo22m:  Redo  the  configuration.   This does nothing the first time
-	 1mgemstash setup 22mis run.  If you want to change your configuration	us-
-	 ing  1mgemstash setup 22mafter you've run it before, you must provide this
+       o --redo:  Redo	the  configuration.   This does nothing the first time
+	 gemstash setup is run.  If you want to change your configuration  us-
+	 ing  gemstash setup after you've run it before, you must provide this
 	 option, otherwise Gemstash will simply indicate your  setup  is  com-
 	 plete.
 
-       o 1m--debug22m:	Output	additional  information if one of the checks at the
+       o --debug:  Output  additional  information if one of the checks at the
 	 end of setup fails.  This will do nothing if all checks pass.
 
-       o 1m--config-file FILE22m: Specify the config file  to  write  to.   Without
-	 this  option,	your configuration will be written to 1m~/.gemstash/con-0m
-	 1mfig.yml22m.	If you write to a custom location, you will  need  to  pass
-	 the  1m--config-file  22moption  to all Gemstash commands.  If you plan to
-	 use ERB in your config file, you might want to  use  1m~/.gemstash/con-0m
-	 1mfig.yml.erb22m.
-
-
+       o --config-file FILE: Specify the config file  to  write  to.   Without
+	 this  option,	your configuration will be written to ~/.gemstash/con-
+	 fig.yml.  If you write to a custom location, you will	need  to  pass
+	 the  --config-file  option  to all Gemstash commands.	If you plan to
+	 use ERB in your config file, you might want to  use  ~/.gemstash/con-
+	 fig.yml.erb.
 
-				October 9, 2015 	     gemstash-setup(1)
+				October 9, 2015 	     4mgemstash-setup24m(1)

data/lib/gemstash/man/gemstash-start.1

@@ -1,41 +1,17 @@
 <!-- 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-start" "1" "October 9, 2015" "" ""
-.hy
 .SH Name
-.PP
 gemstash-start - Starts the Gemstash server
 .SH Synopsis
-.PP
-\f[V]gemstash start [--no-daemonize] [--config-file FILE]\f[R]
+\f[CR]gemstash start [--config-file FILE]\f[R]
 .SH Description
-.PP
 Starts the Gemstash server.
 .SH Options
 .IP \[bu] 2
-\f[V]--config-file FILE\f[R]: Specify the config file to use.
+\f[CR]--config-file FILE\f[R]: Specify the config file to use.
 If you aren\[cq]t using the default config file at
-\f[V]\[ti]/.gemstash/config.yml\f[R] or
-\f[V]\[ti]/.gemstash/config.yml.erb\f[R], then you must specify the
+\f[CR]\[ti]/.gemstash/config.yml\f[R] or
+\f[CR]\[ti]/.gemstash/config.yml.erb\f[R], then you must specify the
 config file via this option.
-.IP \[bu] 2
-\f[V]--no-daemonize\f[R]: The Gemstash server daemonizes itself by
-default.
-Provide this option to instead run the server until \f[V]Ctrl-C\f[R] is
-typed.
-When not daemonized, the log will be output to standard out.

data/lib/gemstash/man/gemstash-start.1.txt

@@ -1,6 +1,4 @@
-gemstash-start(1)					     gemstash-start(1)
-
-
+4mgemstash-start24m(1)						  4mgemstash-start24m(1)
 
 <!-- Automatically generated by Pandoc -->
 
@@ -8,21 +6,15 @@ gemstash-start(1)					     gemstash-start(1)
        gemstash-start - Starts the Gemstash server
 
 1mSynopsis0m
-       1mgemstash start [--no-daemonize] [--config-file FILE]0m
+       gemstash start [--config-file FILE]
 
 1mDescription0m
        Starts the Gemstash server.
 
 1mOptions0m
-       o 1m--config-file  FILE22m:  Specify  the config file to use.  If you aren't
-	 using the default config file at  1m~/.gemstash/config.yml  22mor  1m~/.gem-0m
-	 1mstash/config.yml.erb22m,  then you must specify the config file via this
+       o --config-file	FILE:  Specify	the config file to use.  If you aren't
+	 using the default config file at  ~/.gemstash/config.yml  or  ~/.gem-
+	 stash/config.yml.erb,	then you must specify the config file via this
 	 option.
 
-       o 1m--no-daemonize22m: The Gemstash server  daemonizes  itself  by  default.
-	 Provide  this option to instead run the server until 1mCtrl-C 22mis typed.
-	 When not daemonized, the log will be output to standard out.
-
-
-
-				October 9, 2015 	     gemstash-start(1)
+				October 9, 2015 	     4mgemstash-start24m(1)