fly.io-rails 0.0.1-aarch64-linux

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: cce22da68a7d2a6628085b486d667dc3038e74749dccecdfee5d2aa140b1a584
+  data.tar.gz: 4b1345f7ec5b8fadcda9461020ed77a79bba57722e78e0e1b532b9ec3c244928
+SHA512:
+  metadata.gz: 750d6c71389bb5659a27ab461e252e740e006b6d8f0e71c0cbad928113b8f1737ee4b9c777345e44b1095830e20be0d47a2b5f6c957d8498aafd8e825c9743c9
+  data.tar.gz: 45911dc4440e2af1e9dd1cf64ac5045d3ea8b9dc1b9364b620f23583e3b78ec5ab61fa87a36b18a5a50f1674a68ac9b9b12110ffb4299baf1953ae66c4bacfb2

data/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -0,0 +1,189 @@
+## Purpose
+
+Add [Fly.io](https://fly.io) support to [Rails](https://rubyonrails.org/).
+
+## Status
+
+<u>pre-alpha</u>.
+
+In fact, the gem has not been yet been pushed to the rubygems
+repository as while creating a github repository is an easily reversible act,
+wiping all memory of a mis-named gem is considerably more challenging.
+
+It currently is possible to build the gem files, install the prerequisite
+`ruby-fly` gem, and then install the platform specific gem using `--local`.
+You can also add the gem to your Gemfile using the `path:` argument to the
+`gem` statement/method call.  Of course, all of this will be taken care of
+for you once this gem has been published.
+
+## Quickstart/summary
+
+```sh
+rails new demo
+cd demo
+bundle add fly.io-rails
+flyctl auth login
+bin/rails fly:launch
+bin/rails deploy
+```
+
+## Build instructions
+
+```
+rake package
+```
+
+This will involve downloading binaries from github and building gems for
+every supported platform as well as an additional gem that doesn't
+include a binary.
+
+To download new binaries, run `rake clobber` then `rake package` agein.
+
+## Description
+
+ -  `bundle add fly.io-rails`
+    
+    This will install `ruby-fly` middleware, add new Rails tasks, extend the
+    channel and job generatotors, and platform binaries for
+    [flyctl](https://github.com/superfly/flyctl#readme).  I've followed the
+    trail blazed by [nokogiri](https://nokogiri.org/) and others to make
+    platform binaries happen.
+
+ - `bin/rails fly:launch`
+
+   This won't be a mere front enty to [`flyctl
+   launch`](https://fly.io/docs/flyctl/launch/).  It will use
+   [`thor`](https://github.com/rails/thor#thor) to rewrite the configuration
+   for the `production` environment as well as tweak the `Dockerfile` and
+   `fly.toml` based on your application - in particular the configuration for
+   ActiveRecord, ActiveJob, and ActionCable.  The people at Fly will know what
+   databases and message queing systems work best on their platform and should
+   make it easy to do the right thing.
+
+   As an example, the default production database for a new application in
+   Rails is sqlite3.  Either this will need to be replaced by Postgre in
+   the Rails configuration *or* a volume will need to be defined, mounted,
+   and the Rails configuration modified to point to the new mount point.
+
+   This gem should pick one of those paths as the default, and provide an option to chose other paths.
+
+ - `bin/rails generate channel`, `bin/rails generate job`, etc.
+
+   Rails applications are generally not invented fully formed.  They evolve and
+   add features.  I don't want people to think about having to configure rails
+   AND configure fly when then add features.  Generators that developers
+   already use today should be able to update both the Rails and Fly
+   configurations in a consistent manner.
+
+For now, both the Rails tasks and generators don't actually modify the Rails
+configuratio to support Fly, instead they merely output the string `Configuring
+fly...`.  Let your imagination run wild.
+
+## Motivation
+
+Oversimplifying and exagerating to make a point, `flyctl launch` generates an
+initial fly configuration based on the state of the application at launch time
+but leaves configuring your Rails application up to you.  The initial Fly
+configuration may need to be tweaked, and both the fly and Rails configurations
+will need to be maintained as the application evolves.
+
+From a Rails developer perspective, this makes fly an additional framework that
+must be learned and attended to.
+
+This can all be changed with a single `bundle add` command.  Everything from
+new `rails` tasks to extending the behavior of existing generators to making
+changes to configuration to monkeypatching Rails internals itself are on the
+table.
+
+A few sublte but important mindset changes are necessary to pull this off:
+
+  * Instead of "we support every (or perhaps even only 'most') Rails
+    configuration" the mindset we should strive for is "we provide a default
+    production configuration that works for most, and provide options to add or
+    replace components as desired".
+
+    We should be bold and daring.  We should chose a default web server, a
+    default database, a default active job queue adapter, a default action
+    cable subscription adapter, etc., etc., etc.
+
+    Over time, this should encompas everything needed for monitoring and
+    deployment.  Requirements for things like log file management should be
+    anticipated and accounted for.
+
+  * Any configuration artifact that is generated and needs to be checked into
+    the application's source control repository needs to be [beautiful
+    code](https://rubyonrails.org/doctrine#beautiful-code).  If you look at
+    configuration files provided by either `rails new` or by rails generators,
+    they have comments.  They don't configure things that don't apply to you.
+
+    A concrete example: Rails 7 applications default to import maps.  A
+    `Dockerfile` generated for such an app should not contain code that deals
+    with `yarn` or `node_modules`. 
+
+And as a closing remark - to be fair adding Rails support to Fly and adding Fly
+support to Rails are more complementary than competing efforts.  
+
+## Future
+
+> Que sera, sera
+
+-- Doris Day
+
+I don't know what the future is going to hold, but some guesses:
+
+  * It is plausible that a code base written in Ruby and with access to
+    libraries like [Thos](http://whatisthor.com/) and focused exclusively on
+    Rails may attract more contributions from the Rails community than a
+    codebase written in Go and targetting many disparate frameworks.
+  * Flyctl launch can continue to provide a basic Fly configuration for Rails,
+    but if this effort is successful these configurations would largely be
+    replaced by more tailors configurations that are updated by generators and
+    rake tasks as the application evolves.
+  * Not every flyctl command needs to have a Rails wrapper -- only the common
+    task do.  It is quiet OK for developers to deal directly with fly when it
+    makes sence to do so.  But those flyctl command that are wrapped may need
+    options added that enable them to be run without the need to prompt the
+    user.
+  * This gem could be built and published alongside the flyctl executables, and
+    `flyctl version update` could detect whether or not it was installed as a
+    gem and react appropriately.
+
+## Call to Action
+
+> good ideas and bad code build communities, the other three combinations do
+> not
+
+-- Stefano Mazzocchi
+
+> the best way to get the right answer on the internet is not to ask a
+> question; it's to post the wrong answer.
+
+-- Ward Cunningham
+
+I don't presume that any specific line of code in this initial implementation
+will last the test of time.  Heck, I'm not even confident enough in the
+proposed name to register the gem, though the name does feel *rails-like* -
+just take a look at any Rails `Gemfile` to see.
+
+My hope is that there is enough scaffolding here to not only make clear what
+the possibilities are, but also enough structure so that it is fairly obvious
+where new logic should go, together there is not only enough promise and
+structure to attract a community.
+
+Some starter ideas:
+
+ * Can we make `bin/rails deploy` smart enough to invoke `flyctl auth login` if
+   you are not logged in and `bin/rails fly:launch` if the application had not
+   previously been launched, with the goal of reducing the number of commands a
+   user has to issue to get started.  Also I'm impressed by the way auth login
+   launches a browser, can we do the same for fly launch?
+
+ * While a number of application configuration changes are made through
+   generators, not all are.  For example, upgrading the version of Ruby to be
+   used.  Perhaps we could create tasks for some of these, but likely it will
+   be worthwhile to create a `fly:reconfig` task.
+
+Finally, once this repository is in the superfly github organization and
+a gem has been published, this README should be rewritten from focus on
+raison d'être and to a focus on what value it would bring to those that
+install and use it.

data/Rakefile

@@ -0,0 +1,158 @@
+# coding: utf-8
+#
+#  Rake tasks to manage native gem packages with flyctl binary executables from github
+#
+#  TL;DR: run "rake package"
+#
+#  The native platform gems (defined by Fly_io::PLATFORMS)
+#  will each contain two files in addition to what the vanilla ruby gem contains:
+#
+#     exe/
+#     ├── flyctl                                 #  generic ruby script to find and run the binary
+#     └── <Gem::Platform architecture name>/
+#         └── flyctl                             #  the flyctl binary executable
+#
+#  The ruby script `exe/flyctl` is installed into the user's path, and it simply locates the
+#  binary and executes it. Note that this script is required because rubygems requires that
+#  executables declared in a gemspec must be Ruby scripts.
+#
+#  As a concrete example, an x86_64-linux system will see these files on disk after installing
+#  fly.io-rails-1.x.x-x86_64-linux.gem:
+#
+#     exe/
+#     ├── flyctl     
+#     └── x86_64-linux/
+#         └── flyctl     
+#
+#  So the full set of gem files created will be:
+#
+#  - pkg/fly.io-rails-1.0.0.gem
+#  - pkg/fly.io-rails-1.0.0-arm64-darwin.gem
+#  - pkg/fly.io-rails-1.0.0-x64-mingw32.gem
+#  - pkg/fly.io-rails-1.0.0-x86_64-darwin.gem
+#  - pkg/fly.io-rails-1.0.0-x86_64-linux.gem
+# 
+#  Note that in addition to the native gems, a vanilla "ruby" gem will also be created without
+#  either the `exe/flyctl` script or a binary executable present.
+#
+#
+#  New rake tasks created:
+#
+#  - rake gem:ruby           # Build the ruby gem
+#  - rake gem:arm64-darwin   # Build the arm64-darwin gem
+#  - rake gem:x64-mingw32    # Build the x64-mingw32 gem
+#  - rake gem:x86_64-darwin  # Build the x86_64-darwin gem
+#  - rake gem:x86_64-linux   # Build the x86_64-linux gem
+#  - rake download           # Download all flyctl binaries
+#
+#  Modified rake tasks:
+#
+#  - rake gem                # Build all the gem files
+#  - rake package            # Build all the gem files (same as `gem`)
+#  - rake repackage          # Force a rebuild of all the gem files
+#
+#  Note also that the binary executables will be lazily downloaded when needed, but you can
+#  explicitly download them with the `rake download` command.
+#
+require "bundler/setup"
+require "bundler/gem_tasks"
+require "rubygems/package_task"
+require 'net/http'
+require 'json'
+require 'stringio'
+require 'zip'
+require_relative 'lib/fly.io-rails/platforms'
+
+task default: :package
+
+FLY_IO_RAILS_GEMSPEC = Bundler.load_gemspec("fly.io-rails.gemspec")
+
+gem_path = Gem::PackageTask.new(FLY_IO_RAILS_GEMSPEC).define
+desc "Build the ruby gem"
+task "gem:ruby" => [gem_path]
+
+def fetch(uri, limit = 10)
+  raise ArgumentError, 'HTTP redirect too deep' unless limit > 0
+  response = Net::HTTP.get_response(URI(uri))
+
+  case response
+  when Net::HTTPSuccess
+    response.body
+  when Net::HTTPRedirection
+    fetch(response['location'], limit - 1)
+  else
+    STDERR.puts 'HTTP Error: ' + response.message.to_s
+    exit 1
+  end
+end
+
+exepaths = []
+uri = 'https://api.github.com/repos/superfly/flyctl/releases/latest'
+release = JSON.parse(fetch(uri))
+
+release['assets'].each do |asset|
+  platform = Fly_io::PLATFORMS[asset['name'][/^flyctl_.*?_(.*?)\./, 1]]
+  next unless platform
+
+  FLY_IO_RAILS_GEMSPEC.dup.tap do |gemspec|
+    exedir = File.join(gemspec.bindir, platform) # "exe/x86_64-linux"
+    exepath = File.join(exedir, "flyctl") # "exe/x86_64-linux/flyctl"
+
+    if asset['name'] =~ /Windows/i
+      exepath += '.exe' 
+      dll = File.join(exedir, 'wintun.dll')
+      gemspec.files << dll
+      file dll => exepath
+    end
+
+    exepaths << exepath
+    gemspec.files << exepath
+
+    # modify a copy of the gemspec to include the native executable
+    gemspec.platform = platform
+
+    # create a package task
+    gem_path = Gem::PackageTask.new(gemspec).define
+    desc "Build the #{platform} gem"
+    task "gem:#{platform}" => [gem_path]
+
+    directory exedir
+    file exepath => [exedir] do
+      release_url = asset['browser_download_url']
+      warn "Downloading #{release_url} ..."
+
+      case File.extname(asset['name'])
+      when '.gz'
+	Zlib::GzipReader.wrap(StringIO.new(fetch(release_url))) do |gz|
+	  Gem::Package::TarReader.new(gz) do |tar|
+	    tar.each do |entry|
+              exepath = File.join(exedir, entry.full_name)
+              File.open(exepath, "wb") do |local|
+                local.write(entry.read)
+              end
+              FileUtils.chmod(0755, exepath, verbose: true)
+	    end
+	  end
+	end
+      when '.zip'
+	Zip::File.open_buffer(fetch(release_url)) do |zip_file|
+	  zip_file.each do |entry|
+            exepath = File.join(exedir, entry.name)
+            STDERR.puts exepath
+            File.open(exepath, "wb") do |local|
+              local.write(zip_file.read(entry.name))
+            end
+	  end
+	end
+      end
+    end
+  end
+end
+
+desc "Download all flyctl binaries"
+task download: exepaths
+
+task package: :download
+
+CLOBBER.add(exepaths.map { |path| File.dirname(path) })
+

data/exe/flyctl

@@ -0,0 +1,44 @@
+#! /usr/bin/env ruby
+# because rubygems shims assume a gem's executables are Ruby
+
+require "fly.io-rails/platforms"
+
+supported_platforms = Fly_io::PLATFORMS.values
+platform = [:cpu, :os].map { |m| Gem::Platform.local.send(m) }.join("-")
+
+if supported_platforms.none? { |supported_platform| Gem::Platform.match(supported_platform) }
+  STDERR.puts(<<~ERRMSG)
+    ERROR: flyctl does not support the #{platform} platform
+  ERRMSG
+  exit 1
+end
+
+exe_path = Dir.glob(File.join(__dir__, "*", "flyctl*")).find do |f|
+  Gem::Platform.match(File.basename(File.dirname(f)))
+end
+if exe_path.nil?
+  STDERR.puts(<<~ERRMSG)
+    ERROR: Cannot find the flyctl executable for #{platform} in #{__dir__}
+    If you're using bundler, please make sure you're on the latest bundler version:
+
+      gem install bundler
+      bundle update --bundler
+
+    Then make sure your lock file includes this platform by running:
+
+      bundle lock --add-platform #{platform}
+      bundle install
+
+    See `bundle lock --help` output for details.
+  ERRMSG
+  exit 1
+end
+
+if Gem.win_platform?
+  # use system rather than exec as exec inexplicably fails to find the executable
+  # on Windows
+  system exe_path, *ARGV
+else
+  # use exec rather than system to avoid creating a new process
+  exec exe_path, *ARGV
+end

data/lib/fly.io-rails/generators.rb

@@ -0,0 +1,15 @@
+require 'rails/generators'
+require 'rails/generators/channel/channel_generator'
+require 'rails/generators/job/job_generator'
+
+class Rails::Generators::ChannelGenerator
+  def configure_fly
+    STDERR.puts 'Configuring fly...'
+  end
+end
+
+class Rails::Generators::JobGenerator
+  def configure_fly
+    STDERR.puts 'Configuring fly...'
+  end
+end

data/lib/fly.io-rails/platforms.rb

@@ -0,0 +1,10 @@
+module Fly_io
+  PLATFORMS = {
+    'Linux_arm64' => 'aarch64-linux',
+    'Linux_x86_64' => 'x86-linux',
+    'macOS_arm64' => 'arm64-darwin',
+    'macOS_x86_64' => 'x86_64-darwin',
+    'Windows_arm64' => nil, # Can't find a match
+    'Windows_x86_64' => 'x64-mingw32'
+  }
+end

data/lib/fly.io-rails/version.rb

@@ -0,0 +1,3 @@
+module Fly_io
+  VERSION = '0.0.1'
+end

data/lib/fly.io-rails.rb

@@ -0,0 +1,10 @@
+require 'rails'
+require 'fly.io-rails/generators'
+
+class FlyIoRailtie < Rails::Railtie
+  rake_tasks do
+    Dir[File.expand_path('tasks/*.rake', __dir__)].each do |file|
+      load file
+    end
+  end
+end

data/lib/tasks/fly.rake

@@ -0,0 +1,26 @@
+namespace :fly do
+  desc 'Launch a new app'
+  task :launch do
+    sh 'flyctl launch'
+
+    # note: Rake task argument syntax isn't particularly user friendy,
+    # but Rake is a Ruby program and we have full access to ARGV,
+    # meaning we can do our own thing with OptionParser or whatever.
+    # The only real caveat if we do so is that we need to exit the
+    # program at the completion of the task lest Rails tries to interpet
+    # the next argument as the name of the next task to execute.
+
+    Rake.rake_output_message 'Customizing Dockerfile...'
+
+    exit
+  end
+
+  desc 'Deploy fly application'
+  task :deploy do
+    sh 'flyctl deploy'
+  end
+end
+
+# Alias, for convenience
+desc 'Deploy fly application'
+task deploy: 'fly:deploy'

metadata

@@ -0,0 +1,68 @@
+--- !ruby/object:Gem::Specification
+name: fly.io-rails
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: aarch64-linux
+authors:
+- Sam Ruby
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2022-09-13 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: fly-ruby
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+description:
+email: rubys@intertwingly.net
+executables:
+- flyctl
+extensions: []
+extra_rdoc_files: []
+files:
+- LICENSE
+- README.md
+- Rakefile
+- exe/aarch64-linux/flyctl
+- exe/flyctl
+- lib/fly.io-rails.rb
+- lib/fly.io-rails/generators.rb
+- lib/fly.io-rails/platforms.rb
+- lib/fly.io-rails/version.rb
+- lib/tasks/fly.rake
+homepage: https://github.com/rubys/fly-io.rails
+licenses:
+- Apache-2.0
+metadata:
+  homepage_uri: https://github.com/rubys/fly-io.rails
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.3.22
+signing_key:
+specification_version: 4
+summary: Rails support for Fly-io
+test_files: []