gemstash 2.6.0-java → 2.7.0-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2f9413aec2ce0f9af1d98dc5f56e0bdfe8e974ed4a390a05ee0eb648e4c6d65a
-  data.tar.gz: eeb7f4aa36d4162467c9f20cf69b8c16ad9d5add6f73571c4ec63d24a4562750
+  metadata.gz: e1a0787f0056a3ecc62b1f9a42d1a9b17de0e7dd04078937e4357cd547473856
+  data.tar.gz: 2d820a53d23a6b3d8eaea49ba58f9afd279745926c6b072fb7e695f58871638d
 SHA512:
-  metadata.gz: 7b288f7fa477452839963a78b22d38635dac29a904947c5b04d2d5a67be222e5f1220b253baaf7ac4ca168ee9a8591245bd63d2de80edf52f12cb92bab39d9a2
-  data.tar.gz: f8b30aebbe19b38313e5ad1a6a68b0074865adac73d52fb39a0c7be0f43f36eeae053463ca524786f05ac579d53fed39d3ce54594b0a0a868492213c4af32648
+  metadata.gz: d15376223d9f71771fe63a7b0faa47b0e531fbdd68fc278e7b2fbcc58caebceb02fb2eaaaebf4d095d53cb94ef895f8096b8aba0332aaacafd5001b78e78e513
+  data.tar.gz: f5e26c9cc3ed44a92a142b4e529a62106dd8c31c080db03477b6a48b7cd3bea1c716454dc572d0a4a4f127ce1dc0f7838e116e584aabcb142852dcf2217b1c0c

data/CHANGELOG.md

@@ -1,3 +1,10 @@
+## 2.7.0 (2023-10-08)
+
+### Fixes
+
+  - Fix uninitialized constant error when using Redis cache ([#375](https://github.com/rubygems/gemstash/pull/375), [@chris72205](https://github.com/chris72205))
+  - Remove --daemonize option, no longer supported by Puma. ([#359](https://github.com/rubygems/gemstash/issues/359) [@olleolleolle](https://github.com/olleolleolle))
+
 ## 2.6.0 (2023-09-30)
 
 ### Changes
@@ -20,7 +27,7 @@
 
 ### Fixes
 
-  - Require a now-needed file for Puma 6. Thanks, [@ktreis](https://github.com/ktreis)! ([#362](https://github.com/rubygems/gemstash/pull/362), [@olleolleolle](https://github.com/olleolleolle))
+  - Require a now-needed file for Puma 6. Thanks, @ktreis! ([#362](https://github.com/rubygems/gemstash/pull/362), [@olleolleolle](https://github.com/olleolleolle))
 
 ## 2.3.1 (2023-09-05)
 

data/lib/gemstash/cli/setup.rb

@@ -90,8 +90,8 @@ module Gemstash
 
       def ask_redis_details
         say_current_config(:redis_servers, "Current Redis servers")
-        servers = @cli.ask "What is the comma-separated list of Redis servers? [localhost:6379]"
-        servers = "localhost:6379" if servers.empty?
+        servers = @cli.ask "What is the comma-separated list of Redis servers? [redis://localhost:6379]"
+        servers = "redis://localhost:6379" if servers.empty?
         @config[:redis_servers] = servers
       end
 

data/lib/gemstash/cli/start.rb

@@ -10,47 +10,23 @@ module Gemstash
     class Start < Gemstash::CLI::Base
       def run
         prepare
-        setup_logging
-        store_daemonized
         @cli.say("Starting gemstash!", :green)
         Puma::CLI.new(args, Gemstash::Logging::StreamLogger.puma_events).run
       end
 
     private
 
-      def setup_logging
-        return unless daemonize?
-
-        Gemstash::Logging.setup_logger(gemstash_env.log_file)
-      end
-
-      def store_daemonized
-        Gemstash::Env.daemonized = daemonize?
-      end
-
-      def daemonize?
-        @cli.options[:daemonize]
-      end
-
       def puma_config
         File.expand_path("../puma.rb", __dir__)
       end
 
       def args
-        config_args + pidfile_args + daemonize_args
+        config_args + pidfile_args
       end
 
       def config_args
         ["--config", puma_config]
       end
-
-      def daemonize_args
-        if daemonize?
-          ["--daemon"]
-        else
-          []
-        end
-      end
     end
   end
 end

data/lib/gemstash/cli.rb

@@ -75,8 +75,6 @@ module Gemstash
     end
 
     desc "start", "Starts your gemstash server"
-    method_option :daemonize, :type => :boolean, :default => true, :desc =>
-      "Daemonize the server"
     method_option :config_file, :type => :string, :desc =>
       "Config file to load when starting"
     def start

data/lib/gemstash/config.ru

@@ -6,8 +6,6 @@ require "puma/commonlogger"
 use Rack::Deflater
 use Gemstash::Logging::RackMiddleware
 
-use Puma::CommonLogger, Gemstash::Logging::StreamLogger.for_stdout if Gemstash::Env.daemonized?
-
 use Gemstash::Env::RackMiddleware, Gemstash::Env.current
 use Gemstash::GemSource::RackMiddleware
 use Gemstash::Health::RackMiddleware

data/lib/gemstash/env.rb

@@ -59,17 +59,6 @@ module Gemstash
       Thread.current[:gemstash_env] = value
     end
 
-    def self.daemonized?
-      raise "Daemonized hasn't been set yet!" if @daemonized.nil?
-
-      @daemonized
-    end
-
-    def self.daemonized=(value)
-      value = false if value.nil?
-      @daemonized = value
-    end
-
     def config
       @config ||= Gemstash::Configuration.new
     end

data/lib/gemstash/man/gemstash-configuration.5

@@ -181,6 +181,3 @@ The file will be placed in the base path.
 \f[CR]server.log\f[R]
 .SS Valid values
 Any valid file name, or \f[CR]:stdout\f[R] to log to \f[CR]$stdout\f[R]
-.PP
-\f[I]Note: Using \f[CI]:stdout\f[I] for the \f[CI]:log_file\f[I]
-requires running with \f[CI]--no-daemonize\f[I].\f[R]

data/lib/gemstash/man/gemstash-configuration.5.txt

@@ -202,7 +202,4 @@
    1mValid values0m
        Any valid file name, or :stdout to log to $stdout
 
-       4mNote:24m 4mUsing24m 4m:stdout24m 4mfor24m 4mthe24m 4m:log_file24m 4mrequires24m 4mrunning24m 4mwith24m 4m--no-daemo-0m
-       4mnize.0m
-
 			       October 13, 2015      4mgemstash-configuration24m(5)

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

@@ -10,11 +10,10 @@ 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:
+Gemstash outputs its log directly to standard out:
 .IP
 .EX
-$ gemstash start --no-daemonize
+$ gemstash start
 .EE
 .PP
 You can also check the status of the server:
@@ -24,7 +23,7 @@ $ gemstash status
 .EE
 .PP
 The server status is checked by passing through to
-pumactl (https://github.com/puma/puma#pumactl).
+pumactl (https://github.com/puma/puma#controlstatus-server).
 .PP
 If you find a bug, please don\[cq]t hesitate to open a bug
 report (https://github.com/rubygems/gemstash#contributing)!

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

@@ -8,18 +8,17 @@
        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 di-
-       rectly to standard out:
+       You  might  find  it  easier to view the log directly in your terminal.
+       Gemstash outputs its log directly to standard out:
 
-	      $ gemstash start --no-daemonize
+	      $ gemstash start
 
        You can also check the status of the server:
 
 	      $ gemstash status
 
        The  server  status  is	checked  by   passing	through   to   pumactl
-       (https://github.com/puma/puma#pumactl).
+       (https://github.com/puma/puma#controlstatus-server).
 
        If  you	find  a  bug,  please  don't  hesitate	to  open  a bug report
        (https://github.com/rubygems/gemstash#contributing)!

data/lib/gemstash/man/gemstash-multiple-sources.7

@@ -101,7 +101,7 @@ end
 And run the Gemstash with the credentials set in an ENV variable:
 .IP
 .EX
-GEMSTASH_MY__GEM___SOURCE__LOCAL=user:password gemstash start --no-daemonize --config-file config.yml.erb
+GEMSTASH_MY__GEM___SOURCE__LOCAL=user:password gemstash start --config-file config.yml.erb
 .EE
 .PP
 The name of the ENV variable is the uppercase version of the host name,

data/lib/gemstash/man/gemstash-multiple-sources.7.txt

@@ -88,7 +88,7 @@
 
        And run the Gemstash with the credentials set in an ENV variable:
 
-	      GEMSTASH_MY__GEM___SOURCE__LOCAL=user:password gemstash start --no-daemonize --config-file config.yml.erb
+	      GEMSTASH_MY__GEM___SOURCE__LOCAL=user:password gemstash start --config-file config.yml.erb
 
        The name of the ENV variable is the uppercase version of the host name,
        with all . characters replaced with __, all - with ___ and a  GEMSTASH_

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

@@ -7,7 +7,7 @@
 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
@@ -143,9 +143,9 @@ 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.
+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
 Deep dive into more subjects:
 .IP \[bu] 2
@@ -178,7 +178,7 @@ 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
 After checking out the repo, run \f[CR]bin/setup\f[R] to install
 dependencies.
@@ -192,7 +192,7 @@ 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
 The gem is available as open source under the terms of the MIT

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

@@ -7,11 +7,11 @@
        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,
@@ -20,34 +20,34 @@
        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
+       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-
+       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
+       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.
+       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
@@ -58,7 +58,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
@@ -67,7 +67,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!
@@ -75,51 +75,51 @@
 	      $ 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
 
        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
+       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
+       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
+       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
+       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
+       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
+       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-
+       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:
@@ -153,25 +153,25 @@
 
        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).
+       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 bin/setup to install dependencies.
+       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
+       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
+       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
+       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-start.1

@@ -5,7 +5,7 @@
 .SH Name
 gemstash-start - Starts the Gemstash server
 .SH Synopsis
-\f[CR]gemstash start [--no-daemonize] [--config-file FILE]\f[R]
+\f[CR]gemstash start [--config-file FILE]\f[R]
 .SH Description
 Starts the Gemstash server.
 .SH Options
@@ -15,9 +15,3 @@ 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

@@ -6,7 +6,7 @@
        gemstash-start - Starts the Gemstash server
 
 1mSynopsis0m
-       gemstash start [--no-daemonize] [--config-file FILE]
+       gemstash start [--config-file FILE]
 
 1mDescription0m
        Starts the Gemstash server.
@@ -17,8 +17,4 @@
 	 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/version.rb

@@ -2,5 +2,5 @@
 
 # :nodoc:
 module Gemstash
-  VERSION = "2.6.0"
+  VERSION = "2.7.0"
 end

data/lib/gemstash.rb

@@ -20,6 +20,7 @@ module Gemstash
   autoload :LruReduxClient,      "gemstash/cache"
   autoload :NotAuthorizedError,  "gemstash/authorization"
   autoload :RackEnvRewriter,     "gemstash/rack_env_rewriter"
+  autoload :RedisClient,         "gemstash/cache"
   autoload :Resource,            "gemstash/storage"
   autoload :SpecsBuilder,        "gemstash/specs_builder"
   autoload :Storage,             "gemstash/storage"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: gemstash
 version: !ruby/object:Gem::Version
-  version: 2.6.0
+  version: 2.7.0
 platform: java
 authors:
 - Andre Arko
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-09-30 00:00:00.000000000 Z
+date: 2023-10-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement