puma-plus-core 0.1.0-aarch64-linux

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: e34b1ef06d0a1236642b404801bd239183bb0e0cba40df6d7362b850a6383300
+  data.tar.gz: f030593b78ae07fdd6dd3747c2196a1eeb7a378f1fe55c2371488ec391240357
+SHA512:
+  metadata.gz: 0cf09236c05a70b008aad0022bb1c03874725707856becceb0560808f2bbe4afc80fda2400571fc327dd132d36d0711fab407f77fa61af4a6b9103b9f8904dcf
+  data.tar.gz: 34d5fed444595ac17d639ed67ec000e9400853abadd76be67259b17e9b40c36f4cfe53a23ec2c758f21fb16fcd97c601297a2f00d11451f56226227db30d06ec

data/ext/puma_plus_core/extconf.rb

@@ -0,0 +1,85 @@
+# frozen_string_literal: true
+
+# Builds the Go server at install time.
+#
+# Not a C extension, despite living under ext/ and being named extconf.rb.
+# RubyGems has exactly one hook that runs a build during `gem install`, and this
+# is it -- so the file exists to satisfy that convention, writes a Makefile that
+# runs `go build`, and compiles no C at all.
+#
+# This path only runs for the source gem. A platform gem
+# (puma-plus-core-X.Y.Z-x86_64-linux) ships the binary already built and has no
+# extension, so no Go toolchain is needed for the common install.
+
+require "mkmf"
+require "fileutils"
+
+GEM_ROOT = File.expand_path("../..", __dir__)
+EXE_DIR = File.join(GEM_ROOT, "exe")
+EXE = File.join(EXE_DIR, RbConfig::CONFIG["host_os"] =~ /mswin|mingw/ ? "puma-plus-server.exe" : "puma-plus-server")
+GO_SRC = File.join(GEM_ROOT, "go")
+
+def abort_with(message)
+  # Written to stdout as well: RubyGems shows mkmf.log on failure, but the
+  # reason belongs where someone will actually see it.
+  warn message
+  File.write("Makefile", "all:\n\t@echo '#{message.lines.first.strip}'; exit 1\n")
+  exit 1
+end
+
+go = find_executable0("go")
+unless go
+  abort_with(<<~MSG)
+    puma-plus-core: no Go toolchain found, and no prebuilt binary ships for this platform.
+
+    Either install Go #{PumaPlusGoMinimum = '1.24'} or newer, or install a platform-specific gem if one
+    exists for #{RUBY_PLATFORM}.
+  MSG
+end
+
+version = `#{go} version`.to_s[/go(\d+)\.(\d+)/, 0].to_s
+unless version.empty?
+  major, minor = version.sub("go", "").split(".").map(&:to_i)
+  if major < 1 || (major == 1 && minor < 24)
+    abort_with("puma-plus-core: Go #{version} is too old; 1.24 or newer is required.")
+  end
+end
+
+unless File.directory?(GO_SRC)
+  abort_with("puma-plus-core: the gem is missing its Go sources at #{GO_SRC}.")
+end
+
+FileUtils.mkdir_p(EXE_DIR)
+
+# A Makefile rather than shelling out here, so the build runs in the phase
+# RubyGems expects and its output is captured the way a compile would be.
+#
+# The three-target shape matters and is not decoration. RubyGems runs
+# `make clean`, `make`, `make install`, and then `make clean` AGAIN. A Makefile
+# whose clean target removes the installed binary therefore deletes its own
+# output on that last pass and reports success -- which is exactly what happened
+# here: the gem installed, said nothing, and shipped an empty exe/ directory.
+#
+# So this mirrors what a C extension does. The build writes into this directory,
+# install copies it out to exe/, and clean only removes the local copy.
+#
+# -mod=vendor is deliberate: the gem vendors its dependencies, so the build is
+# offline and reproducible. An install that reached out to proxy.golang.org
+# would fail in exactly the sandboxed and air-gapped environments people deploy
+# from.
+LOCAL = File.join(Dir.pwd, File.basename(EXE))
+
+File.write("Makefile", <<~MAKE)
+  all:
+  \tcd #{GO_SRC} && #{go} build -mod=vendor -trimpath -ldflags "-s -w" -o #{LOCAL} ./cmd/puma-plus
+
+  install: all
+  \tmkdir -p #{EXE_DIR}
+  \tcp #{LOCAL} #{EXE}
+  \t@echo "puma-plus-core: installed #{EXE}"
+
+  clean:
+  \trm -f #{LOCAL}
+MAKE
+
+puts "puma-plus-core: will build #{EXE} with #{go}"

data/lib/puma_plus/core/version.rb

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+module PumaPlus
+  module Core
+    # Released in lockstep with puma-plus, which depends on this exact version.
+    #
+    # The Go server and the Ruby gem speak a private binary protocol with no
+    # version negotiation in the data path, so a mismatched pair is not a
+    # degraded install -- it is a broken one. Pinning exactly is cheaper than
+    # building negotiation for a pair that is always released together.
+    VERSION = "0.1.0"
+  end
+end

data/lib/puma_plus/core.rb

@@ -0,0 +1,60 @@
+# frozen_string_literal: true
+
+require "rbconfig"
+
+module PumaPlus
+  # Locates the compiled puma-plus server binary.
+  #
+  # This gem exists so that the Go server can be installed by RubyGems like
+  # anything else. It ships two ways:
+  #
+  #   puma-plus-core-X.Y.Z.gem                  source; builds Go at install time
+  #   puma-plus-core-X.Y.Z-x86_64-linux.gem     the binary, already built
+  #
+  # A platform gem is preferred by RubyGems automatically when one matches, so
+  # the common case installs a binary and never needs a Go toolchain. The source
+  # gem is the fallback for platforms nobody has published, and it is the reason
+  # this is a separate gem from puma-plus at all: a native-platform gem can carry
+  # a precompiled Go binary only if it carries nothing that also needs compiling
+  # for the local Ruby, and puma-plus has a C extension that does.
+  module Core
+    # Where the binary lives once installed, either way it got there.
+    def self.binary_path
+      candidates.find { |p| File.executable?(p) && !File.directory?(p) }
+    end
+
+    def self.binary_path!
+      binary_path || raise(<<~MSG)
+        puma-plus-core is installed but has no server binary for this platform.
+
+        Looked in:
+        #{candidates.map { |c| "  #{c}" }.join("\n")}
+
+        If this is a source install, the Go build did not produce a binary --
+        check the output of `gem install puma-plus-core`. A Go toolchain
+        (#{GO_MINIMUM}+) is required to build from source.
+      MSG
+    end
+
+    GO_MINIMUM = "1.24"
+
+    # exe/ is where both paths converge: the source build writes its output
+    # there so that a source install and a platform install are indistinguishable
+    # to everything downstream.
+    def self.candidates
+      root = File.expand_path("../..", __dir__)
+      [
+        File.join(root, "exe", exe_name),
+        File.join(root, "bin", exe_name)
+      ]
+    end
+
+    def self.exe_name
+      windows? ? "puma-plus-server.exe" : "puma-plus-server"
+    end
+
+    def self.windows?
+      RbConfig::CONFIG["host_os"] =~ /mswin|mingw|cygwin/
+    end
+  end
+end

metadata

@@ -0,0 +1,49 @@
+--- !ruby/object:Gem::Specification
+name: puma-plus-core
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: aarch64-linux
+authors:
+- Evan Phoenix
+bindir: bin
+cert_chain: []
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies: []
+description: |
+  The Go half of puma-plus: the HTTP/1.1, HTTP/2 and HTTP/3 frontend, the
+  request queue, and the scaling controller. Installed as a dependency of the
+  puma-plus gem; there is no reason to install it directly.
+email:
+- evan@miren.dev
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- exe/puma-plus-server
+- ext/puma_plus_core/extconf.rb
+- lib/puma_plus/core.rb
+- lib/puma_plus/core/version.rb
+homepage: https://github.com/evanphx/puma-plus
+licenses:
+- MIT
+metadata:
+  source_code_uri: https://github.com/evanphx/puma-plus/tree/v0.1.0
+  rubygems_mfa_required: 'true'
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 3.2.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 4.0.16
+specification_version: 4
+summary: The puma-plus server binary
+test_files: []