gemstash 1.0.0.pre.1-java → 2.6.0-java

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

@@ -0,0 +1,199 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-readme" "7" "November 30, 2015" "" ""
+.SH Gemstash
+.SS What is Gemstash?
+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
+have access to a server within your control, you might want to use
+Gemstash.
+.PP
+If you produce gems that you don\[cq]t want everyone in the world to
+have access to, you might want to use Gemstash.
+.PP
+If you frequently bundle the same set of gems across multiple projects,
+you might want to use Gemstash.
+.PP
+Are you only using gems from https://rubygems.org, and don\[cq]t bundle
+the same gems frequently?
+Well, maybe you don\[cq]t need Gemstash\&...
+yet.
+.PP
+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
+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.
+.PP
+Install Gemstash to get started:
+.IP
+.EX
+$ gem install gemstash
+.EE
+.PP
+After it is installed, starting Gemstash requires no additional steps.
+Simply start the Gemstash server with the \f[CR]gemstash\f[R] command:
+.IP
+.EX
+$ gemstash start
+.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
+With the server running, you can bundle against it.
+Tell Bundler that you want to use Gemstash to find gems from
+RubyGems.org:
+.IP
+.EX
+$ bundle config mirror.https://rubygems.org http://localhost:9292
+.EE
+.PP
+Now you can create a Gemfile and install gems through Gemstash:
+.IP
+.EX
+# ./Gemfile
+source \[dq]https://rubygems.org\[dq]
+gem \[dq]rubywarrior\[dq]
+.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
+.EX
+$ bundle install --path .bundle
+.EE
+.PP
+Your Gemstash server has fetched the gems from https://rubygems.org and
+cached them for you!
+To prove this, you can disable your Internet connection 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
+connection:
+.IP
+.EX
+$ # Disable your Internet first!
+$ rm -rf Gemfile.lock .bundle
+$ bundle
+.EE
+.SS Falling back to rubygems.org
+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
+.EX
+$ bundle config mirror.https://rubygems.org.fallback_timeout true
+.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
+.EX
+$ bundle config mirror.https://rubygems.org.fallback_timeout 3
+.EE
+.SS Stopping the Server
+Once you\[cq]ve finish using your Gemstash server, you can stop it just
+as easily as you started it:
+.IP
+.EX
+$ gemstash stop
+.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
+.EX
+$ bundle config --delete mirror.https://rubygems.org
+.EE
+.SS Under the Hood
+You might wonder where the gems are stored.
+After running the commands above, you will find a new directory at
+\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[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
+Gemstash temporarily caches things like gem dependencies in memory.
+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[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.
+.SS Deep Dive
+Deep dive into more subjects:
+.IP \[bu] 2
+Private gems
+.IP \[bu] 2
+Multiple gem sources
+.IP \[bu] 2
+Using Gemstash as a mirror
+.IP \[bu] 2
+Customizing the server (database, storage, caching, and more)
+.IP \[bu] 2
+Deploying Gemstash
+.IP \[bu] 2
+Debugging Gemstash
+.SS Reference
+An anatomy of various configuration and commands:
+.IP \[bu] 2
+Configuration
+.IP \[bu] 2
+Authorize
+.IP \[bu] 2
+Start
+.IP \[bu] 2
+Stop
+.IP \[bu] 2
+Status
+.IP \[bu] 2
+Setup
+.IP \[bu] 2
+Version
+.PP
+To see what has changed in recent versions of Gemstash, see the
+CHANGELOG (https://github.com/rubygems/gemstash/blob/master/CHANGELOG.md).
+.SS Development
+After checking out the repo, run \f[CR]bin/setup\f[R] to install
+dependencies.
+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
+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)
+code of conduct.
+.SS License
+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

@@ -0,0 +1,177 @@
+4mgemstash-readme24m(7) 					 4mgemstash-readme24m(7)
+
+<!-- Automatically generated by Pandoc -->
+
+1mGemstash0m
+   1mWhat is Gemstash?0m
+       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 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,
+       you might want to use Gemstash.
+
+       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 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
+       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 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
+       server runs on port 9292.
+
+   1mBundling0m
+       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
+
+       Now you can create a Gemfile and install gems through Gemstash:
+
+	      # ./Gemfile
+	      source "https://rubygems.org"
+	      gem "rubywarrior"
+
+       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
+
+       Your Gemstash server has fetched the gems from https://rubygems.org and
+       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-
+       tion:
+
+	      $ # Disable your Internet first!
+	      $ rm -rf Gemfile.lock .bundle
+	      $ 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
+       can easily configure Bundler to fallback to https://rubygems.org.
+
+	      $ bundle config mirror.https://rubygems.org.fallback_timeout true
+
+       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:
+
+	      $ bundle config mirror.https://rubygems.org.fallback_timeout 3
+
+   1mStopping the Server0m
+       Once you've finish using your Gemstash server, you can stop it just  as
+       easily as you started it:
+
+	      $ gemstash stop
+
+       You'll  also  want  to tell Bundler that it can go back to getting gems
+       from RubyGems.org directly, instead of going through Gemstash:
+
+	      $ bundle config --delete mirror.https://rubygems.org
+
+   1mUnder the Hood0m
+       You might wonder where the gems are stored.  After running the commands
+       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 ~/.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 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.
+
+   1mDeep Dive0m
+       Deep dive into more subjects:
+
+       o Private gems
+
+       o Multiple gem sources
+
+       o Using Gemstash as a mirror
+
+       o Customizing the server (database, storage, caching, and more)
+
+       o Deploying Gemstash
+
+       o Debugging Gemstash
+
+   1mReference0m
+       An anatomy of various configuration and commands:
+
+       o Configuration
+
+       o Authorize
+
+       o Start
+
+       o Stop
+
+       o Status
+
+       o Setup
+
+       o Version
+
+       To  see	what  has  changed  in	recent	versions  of Gemstash, see the
+       CHANGELOG	       (https://github.com/rubygems/gemstash/blob/mas-
+       ter/CHANGELOG.md).
+
+   1mDevelopment0m
+       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
+       to adhere to the Contributor Covenant (https://github.com/rubygems/gem-
+       stash/blob/master/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	    4mgemstash-readme24m(7)

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

@@ -0,0 +1,38 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-setup" "1" "October 9, 2015" "" ""
+.SH Name
+gemstash-setup - Customize your Gemstash configuration interactively
+.SH Synopsis
+\f[CR]gemstash setup [--redo] [--debug] [--config-file FILE]\f[R]
+.SH Description
+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
+.EX
+gemstash setup
+gemstash setup --redo
+gemstash setup --config-file <file>
+.EE
+.SH Options
+.IP \[bu] 2
+\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[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[CR]--config-file FILE\f[R]: Specify the config file to write to.
+Without this option, your configuration will be written to
+\f[CR]\[ti]/.gemstash/config.yml\f[R].
+If you write to a custom location, you will need to pass the
+\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[CR]\[ti]/.gemstash/config.yml.erb\f[R].

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

@@ -0,0 +1,38 @@
+4mgemstash-setup24m(1)						  4mgemstash-setup24m(1)
+
+<!-- Automatically generated by Pandoc -->
+
+1mName0m
+       gemstash-setup - Customize your Gemstash configuration interactively
+
+1mSynopsis0m
+       gemstash setup [--redo] [--debug] [--config-file FILE]
+
+1mDescription0m
+       Customize  your	Gemstash  configuration interactively.	This will save
+       your config file, but only if a few checks pass after  you've  provided
+       your answers.
+
+   1mUsage0m
+	      gemstash setup
+	      gemstash setup --redo
+	      gemstash setup --config-file <file>
+
+1mOptions0m
+       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 --debug:  Output  additional  information if one of the checks at the
+	 end of setup fails.  This will do nothing if all checks pass.
+
+       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 	     4mgemstash-setup24m(1)

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

@@ -0,0 +1,23 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-start" "1" "October 9, 2015" "" ""
+.SH Name
+gemstash-start - Starts the Gemstash server
+.SH Synopsis
+\f[CR]gemstash start [--no-daemonize] [--config-file FILE]\f[R]
+.SH Description
+Starts the Gemstash server.
+.SH Options
+.IP \[bu] 2
+\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[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[CR]--no-daemonize\f[R]: The Gemstash server daemonizes itself by
+default.
+Provide this option to instead run the server until \f[CR]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

@@ -0,0 +1,24 @@
+4mgemstash-start24m(1)						  4mgemstash-start24m(1)
+
+<!-- Automatically generated by Pandoc -->
+
+1mName0m
+       gemstash-start - Starts the Gemstash server
+
+1mSynopsis0m
+       gemstash start [--no-daemonize] [--config-file FILE]
+
+1mDescription0m
+       Starts the Gemstash server.
+
+1mOptions0m
+       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 --no-daemonize: The Gemstash server  daemonizes  itself  by  default.
+	 Provide  this option to instead run the server until Ctrl-C is typed.
+	 When not daemonized, the log will be output to standard out.
+
+				October 9, 2015 	     4mgemstash-start24m(1)

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

@@ -0,0 +1,17 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-status" "1" "October 28, 2015" "" ""
+.SH Name
+gemstash-status - Checks status of the Gemstash server
+.SH Synopsis
+\f[CR]gemstash status [--config-file FILE]\f[R]
+.SH Description
+Checks status of the Gemstash server.
+.SH Options
+.IP \[bu] 2
+\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[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.

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

@@ -0,0 +1,20 @@
+4mgemstash-status24m(1) 					 4mgemstash-status24m(1)
+
+<!-- Automatically generated by Pandoc -->
+
+1mName0m
+       gemstash-status - Checks status of the Gemstash server
+
+1mSynopsis0m
+       gemstash status [--config-file FILE]
+
+1mDescription0m
+       Checks status of the Gemstash server.
+
+1mOptions0m
+       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.
+
+			       October 28, 2015 	    4mgemstash-status24m(1)

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

@@ -0,0 +1,17 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-stop" "1" "October 9, 2015" "" ""
+.SH Name
+gemstash-stop - Stops the Gemstash server
+.SH Synopsis
+\f[CR]gemstash stop [--config-file FILE]\f[R]
+.SH Description
+Stops the Gemstash server.
+.SH Options
+.IP \[bu] 2
+\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[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.

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

@@ -0,0 +1,20 @@
+4mgemstash-stop24m(1)						   4mgemstash-stop24m(1)
+
+<!-- Automatically generated by Pandoc -->
+
+1mName0m
+       gemstash-stop - Stops the Gemstash server
+
+1mSynopsis0m
+       gemstash stop [--config-file FILE]
+
+1mDescription0m
+       Stops the Gemstash server.
+
+1mOptions0m
+       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.
+
+				October 9, 2015 	      4mgemstash-stop24m(1)

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

@@ -0,0 +1,17 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-version" "1" "December 14, 2015" "" ""
+.SH Name
+gemstash-version - Show what version of Gemstash you are using
+.SH Synopsis
+\f[CR]gemstash version\f[R]
+.SH Description
+Show what version of Gemstash you are using.
+.SS Usage
+.IP
+.EX
+gemstash version
+gemstash --version
+gemstash -v
+.EE

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

@@ -0,0 +1,19 @@
+4mgemstash-version24m(1)					4mgemstash-version24m(1)
+
+<!-- Automatically generated by Pandoc -->
+
+1mName0m
+       gemstash-version - Show what version of Gemstash you are using
+
+1mSynopsis0m
+       gemstash version
+
+1mDescription0m
+       Show what version of Gemstash you are using.
+
+   1mUsage0m
+	      gemstash version
+	      gemstash --version
+	      gemstash -v
+
+			       December 14, 2015	   4mgemstash-version24m(1)

data/lib/gemstash/migrations/01_gem_dependencies.rb

@@ -1,8 +1,10 @@
+# frozen_string_literal: true
+
 Sequel.migration do
   change do
     create_table :rubygems do
       primary_key :id
-      String :name, :size => 255, :null => false
+      String :name, :size => 191, :null => false
       DateTime :created_at, :null => false
       DateTime :updated_at, :null => false
       index [:name], :unique => true
@@ -11,17 +13,17 @@ Sequel.migration do
     create_table :versions do
       primary_key :id
       Integer :rubygem_id, :null => false
-      String :storage_id, :size => 255, :null => false
-      String :number, :size => 255, :null => false
-      String :platform, :size => 255, :null => false
-      String :full_name, :size => 255, :null => false
+      String :storage_id, :size => 191, :null => false
+      String :number, :size => 191, :null => false
+      String :platform, :size => 191, :null => false
+      String :full_name, :size => 191, :null => false
       TrueClass :indexed, :default => true, :null => false
       TrueClass :prerelease, :null => false
       DateTime :created_at, :null => false
       DateTime :updated_at, :null => false
-      index [:rubygem_id, :number, :platform], :unique => true
+      index %i[rubygem_id number platform], :unique => true
       index [:indexed]
-      index [:indexed, :prerelease]
+      index %i[indexed prerelease]
       index [:number]
       index [:full_name], :unique => true
       index [:storage_id], :unique => true
@@ -30,8 +32,8 @@ Sequel.migration do
     create_table :dependencies do
       primary_key :id
       Integer :version_id, :null => false
-      String :rubygem_name, :size => 255, :null => false
-      String :requirements, :size => 255, :null => false
+      String :rubygem_name, :size => 191, :null => false
+      String :requirements, :size => 191, :null => false
       DateTime :created_at, :null => false
       DateTime :updated_at, :null => false
       index [:version_id]

data/lib/gemstash/migrations/02_authorizations.rb

@@ -1,9 +1,11 @@
+# frozen_string_literal: true
+
 Sequel.migration do
   change do
     create_table :authorizations do
       primary_key :id
-      String :auth_key, :size => 2056, :null => false
-      String :permissions, :size => 255, :null => false
+      String :auth_key, :size => 191, :null => false
+      String :permissions, :size => 191, :null => false
       DateTime :created_at, :null => false
       DateTime :updated_at, :null => false
       index [:auth_key], :unique => true