jets_bb_fork 0.0.4

data/lib/jets/commands/help/routes.md

@@ -0,0 +1,16 @@
+## Example
+
+    $ jets routes
+    +--------+----------------+--------------------+
+    |  Verb  |      Path      | Controller#action  |
+    +--------+----------------+--------------------+
+    | GET    | posts          | posts#index        |
+    | GET    | posts/new      | posts#new          |
+    | GET    | posts/:id      | posts#show         |
+    | POST   | posts          | posts#create       |
+    | GET    | posts/:id/edit | posts#edit         |
+    | PUT    | posts/:id      | posts#update       |
+    | DELETE | posts/:id      | posts#delete       |
+    | ANY    | *catchall      | jets/public#show   |
+    +--------+----------------+--------------------+
+    $

data/lib/jets/commands/help/runner.md

@@ -0,0 +1,17 @@
+## Examples
+
+    $ jets runner 'puts "hi"'
+    hi
+    $ jets runner 'puts Jets.env'
+    development
+
+Using a script in a file.  Let's say you have a script:
+
+script.rb:
+
+```ruby
+puts "hello world: #{Jets.env}"
+```
+
+    $ jets runner file://script.rb
+    hello world: development

data/lib/jets/commands/help/server.md

@@ -0,0 +1,15 @@
+The local server for mimics API Gateway and provides a way to test your app locally without deploying to AWS.
+
+## Examples
+
+    $ jets server
+    => bundle exec shotgun --port 8888 --host 127.0.0.1
+    Jets booting up in development mode!
+    == Shotgun/WEBrick on http://127.0.0.1:8888/
+    [2018-08-17 05:31:33] INFO  WEBrick 1.4.2
+    [2018-08-17 05:31:33] INFO  ruby 2.5.1 (2018-03-29) [x86_64-linux]
+    [2018-08-17 05:31:33] INFO  WEBrick::HTTPServer#start: pid=27433 port=8888
+
+Start up server binding to host `0.0.0.0`:
+
+    jets server --host 0.0.0.0

data/lib/jets/commands/help/status.md

@@ -0,0 +1,14 @@
+The CloudFormation stack status info. Essentially the events of the CloudFormation stack since the last update. If the CloudFormation stack is currently updating, this will live tail the events logs.
+
+## Example
+
+    $ jets status
+    The current status for the stack demo-dev is UPDATE_COMPLETE
+    Stack events:
+    05:21:42AM UPDATE_IN_PROGRESS AWS::CloudFormation::Stack demo-dev User Initiated
+    05:21:45AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiGateway
+    ...
+    05:23:22AM CREATE_COMPLETE AWS::CloudFormation::Stack JetsPreheatJob
+    05:23:25AM UPDATE_COMPLETE_CLEANUP_IN_PROGRESS AWS::CloudFormation::Stack demo-dev
+    05:23:25AM UPDATE_COMPLETE AWS::CloudFormation::Stack demo-dev
+    $

data/lib/jets/commands/help/upgrade.md

@@ -0,0 +1,5 @@
+Upgrades the Jets project structure to the latest version. This command is designed to be idempotent, so it should be safe to run this command multiple times.
+
+## Example
+
+    $ jets upgrade

data/lib/jets/commands/help/url.md

@@ -0,0 +1,6 @@
+If routes have been configured and an API Gateway was created for the app, this provides the application's url.
+
+## Example
+
+    $ jets url
+    https://v9wa7vqcia.execute-api.us-west-2.amazonaws.com/dev

data/lib/jets/commands/import.rb

@@ -0,0 +1,12 @@
+module Jets::Commands
+  class Import < Jets::Commands::Base
+    Jets::Commands::Import::Base.cli_options.each do |args|
+      class_option(*args)
+    end
+    long_desc Help.text('import:rails')
+    register(Jets::Commands::Import::Rails, "rails", "rails", "Imports rails project in the rack subfolder")
+
+    long_desc Help.text('import:rack')
+    register(Jets::Commands::Import::Rack, "rack", "rack", "Imports rack project in the rack subfolder")
+  end
+end

data/lib/jets/commands/import/base.rb

@@ -0,0 +1,49 @@
+class Jets::Commands::Import
+  class Base < Sequence
+    # Ugly, but when the class_option is only defined in the Thor::Group class
+    # it doesnt show up with jets new help :(
+    # If anyone knows how to fix this let me know.
+    def self.cli_options
+      [
+        [:submodule, type: :boolean, default: false, desc: "Imports the project as a submodule"],
+      ]
+    end
+    cli_options.each { |args| class_option(*args) }
+
+    # Since setup is public it will automatically run in the subclasses
+    def setup
+      start_message
+      create_rack_folder
+      configure_ruby
+      create_rackup_wrappers
+    end
+
+  private
+    def start_message
+      puts "Importing app into the rack folder..."
+    end
+
+    def create_rack_folder
+      repo? ? clone_project : copy_project
+    end
+
+    def configure_ruby
+      gsub_file 'rack/Gemfile', /^ruby(.*)/, '# ruby\1' # comment out ruby declaration
+      create_file "rack/.ruby-version", RUBY_VERSION, force: true
+    end
+
+    def create_rackup_wrappers
+      path = File.expand_path("../../builders/rackup_wrappers", File.dirname(__FILE__))
+      Dir.glob("#{path}/*").each do |p|
+        FileUtils.cp(p, "#{rack_folder}/bin/")
+      end
+      chmod "#{rack_folder}/bin/rackup", 0755
+    end
+
+    def bundle_install
+      Bundler.with_clean_env do
+        run "cd rack && bundle install"
+      end
+    end
+  end
+end

data/lib/jets/commands/import/cheatsheet.rb

@@ -0,0 +1,35 @@
+class Jets::Commands::Import
+  class Cheatsheet
+    def self.create(rack_repo_url)
+      new(rack_repo_url).create
+    end
+
+    def initialize(rack_repo_url)
+      @rack_repo_url = rack_repo_url
+    end
+
+    def create
+      path = File.expand_path("./templates/", File.dirname(__FILE__)) + "/submodules-cheatsheet.md"
+      basename = File.basename(path)
+      dest = "#{Jets.root}/#{basename}"
+      cheatsheet = Jets::Erb.result(path, cheatsheet_vars)
+      FileUtils.mkdir_p(File.dirname(dest))
+      IO.write(dest, cheatsheet)
+      puts "Created #{basename} to help with using submodules."
+    end
+
+    def cheatsheet_vars
+      import_command = ARGV[0]
+      {
+        import_command: import_command,
+        rack_repo_url: @rack_repo_url,
+        jets_project_repo_url: jets_project_repo_url,
+      }
+    end
+
+    def jets_project_repo_url
+      # Thanks: https://stackoverflow.com/questions/4089430/how-can-i-determine-the-url-that-a-local-git-repository-was-originally-cloned-fr/4089452
+      `git config --get remote.origin.url`.strip rescue 'https://github.com/user/repo'
+    end
+  end
+end

data/lib/jets/commands/import/rack.rb

@@ -0,0 +1,16 @@
+class Jets::Commands::Import
+  class Rack < Base
+    def install
+      bundle_install
+    end
+
+    def finish_message
+      puts <<~EOL
+        #{"="*30}
+        Congrats! The Rack project from #{@source} has been imported to the rack folder.
+
+        Note, generic rack projects will likely need some adjustments to take into account API Gateway stages and logging. For more info refer to [Mega Mode Considerations](http://rubyonjets.com//megamode-details/).
+      EOL
+    end
+  end
+end

data/lib/jets/commands/import/rails.rb

@@ -0,0 +1,74 @@
+class Jets::Commands::Import
+  class Rails < Base
+    # We add jets-rails gem even though it's only activated within the megamode
+    # rackup wrapper script so user can check run bundle install and determine early
+    # if dependencies are met. The jets-rails gem is also added as part of the deploy
+    # process but we add it here also so the user gets earlier possible errors and
+    # can fix before they hit the deploy phase.
+    def configure_gemfile
+      append_to_file 'rack/Gemfile' do
+        %Q|gem "jets-rails"\n|
+      end
+    end
+
+    def install
+      bundle_install
+    end
+
+    def configure_routes
+      # comment out current catchall route
+      comment_lines("config/routes.rb", 'any[ (][\'"]\*', verbose: true) # any "*catchall", to: ...
+
+      # Add catchall route for rack
+      insert_into_file "config/routes.rb", :before => /^end/ do
+        <<-CODE
+  # Enables Mega Mode Rails integration
+  any "*catchall", to: "jets/rack#process"
+CODE
+      end
+    end
+
+    def reconfigure_database_yml
+      Jets::Turbo::DatabaseYaml.new.reconfigure
+    end
+
+    def finish_message
+      puts <<~EOL
+        #{"="*30}
+        Congrats! The Rails project from #{@source} has been imported to the rack folder.  Here are some next steps:
+
+        # Local Testing
+
+        Check out the config/routes.rb file and noticed how a new catchall route has been added.  It looks something like this:
+
+            any "*catchall", to: "jets/rack#process"
+
+        The catchall route passes any route not handled by the Jets app as a request onto the Rails app.  You can modified the route to selectively route what you want.
+
+        Please double check that rack/config/database.yml is appropriately configured, it likely needs to be updated.
+
+        Test the application locally. Test that the Rails app in the rack subfolder works independently.  You can start the application up with:
+
+            cd rack # cd into the imported Rails project
+            bundle exec rackup
+
+        The rack server starts up on http://localhost:9292
+
+        Once tested, stop that server with CTRL-C.
+
+        Then you can start the jets server from the main jets project:
+
+            cd .. # back to the main jets projet
+            jets server # starts both jets and rack servers
+
+        The jets server starts up on http://localhost:8888  You can stop both servers with CTRL-C.
+
+        # Deploy
+
+        When you are ready deploy to AWS Lambda with:
+
+            jets deploy
+        EOL
+    end
+  end
+end

data/lib/jets/commands/import/sequence.rb

@@ -0,0 +1,90 @@
+require 'bundler'
+require 'fileutils'
+require 'thor'
+
+class Jets::Commands::Import
+  class Sequence < Thor::Group
+    include Thor::Actions
+    argument :source
+
+  private
+    def clone_project
+      if File.exist?(rack_folder)
+        abort "The folder #{rack_folder} already exists.  Please remove it first if you want to import a project."
+      end
+
+      check_git_installed
+      if @options[:submodule]
+        git_submodule
+      else
+        git_clone
+      end
+    end
+
+    def git_submodule
+      puts "Adding project as a submodule"
+      run "git submodule add --force #{repo_url} #{rack_folder}"
+      Cheatsheet.create(repo_url)
+    end
+
+    def git_clone
+      command = "git clone #{repo_url} #{rack_folder}"
+      # Thor's run already puts out the command, so no need to puts
+      run command
+      run "rm -rf #{Jets.root}rack/.git"
+    end
+
+    def copy_project
+      puts "Creating rack folder"
+      template_path = File.expand_path(@source)
+      set_source_paths(template_path)
+      begin
+        directory ".", rack_folder, exclude_pattern: %r{.git}
+      rescue Thor::Error => e
+        puts e.message.color(:red)
+        exit 1
+      end
+    end
+
+    def set_source_paths(*paths)
+      # Using string with instance_eval because block doesnt have access to
+      # path at runtime.
+      self.class.instance_eval %{
+        def self.source_paths
+          #{paths.flatten.inspect}
+        end
+      }
+    end
+
+    # normalize repo_url
+    def repo_url
+      if repo?
+        @source # leave as is, user has provided full github url
+      else
+        # Defaults to GitHub
+        "https://github.com/#{@source}"
+      end
+    end
+
+    def repo?
+      @source.include?('github.com') ||
+      @source.include?('bitbucket.org') ||
+      @source.include?('gitlab.com')
+    end
+
+    def check_git_installed
+      return unless repo_url.include?('http') || repo_url.include?('git@')
+      unless git_installed?
+        abort "Unable to detect git installation on your system.  Git needs to be installed in order to clone the project."
+      end
+    end
+
+    def git_installed?
+      system("type git > /dev/null 2>&1")
+    end
+
+    def rack_folder
+      "#{Jets.root}/rack"
+    end
+  end
+end

data/lib/jets/commands/import/templates/config/database.yml

@@ -0,0 +1,26 @@
+default: &default
+  adapter:  <%= @adapter %>
+  encoding: utf8
+  pool: <%%= ENV["DB_POOL"] || 5  %>
+  database: <%%= ENV['DB_NAME'] || '<%= @database_development %>' %>
+<% if @adapter == 'postgresql' -%>
+  username: <%%= ENV['DB_USER'] || ENV['USER'] %>
+<% else -%>
+  username: <%%= ENV['DB_USER'] || 'root' %>
+<% end -%>
+  password: <%%= ENV['DB_PASS'] %>
+  host: <%%= ENV["DB_HOST"] %>
+  url: <%%= ENV['DATABASE_URL'] %> # takes higher precedence than other settings
+
+development:
+  <<: *default
+  database: <%%= ENV['DB_NAME'] || '<%= @database_development %>' %>
+
+test:
+  <<: *default
+  database: <%= @database_test %>
+
+production:
+  <<: *default
+  database: <%= @database_production %>
+  url: <%%= ENV['DATABASE_URL'] %>

data/lib/jets/commands/import/templates/submodules-cheatsheet.md

@@ -0,0 +1,89 @@
+# Git Submodule Cheatsheet
+
+Git submodules take a little bit of getting used to. This is a cheatsheet for Git Submodules to help learn how to use them.  This file was generated as part of the `jets <%= @import_command %>` command.
+
+## Cheatsheet Summary
+
+The important submodule commands are:
+
+### On fresh clone project
+
+    git clone <%= @jets_project_repo_url %>
+    git submodule init # required on a fresh clone, or update won't do anything
+    git submodule update # syncs submodule rack folder with what parent project has as commits
+
+### Updating
+
+After doing a git pull on the Jets main project, you might notice changes to the submodule rack folder, you can update the rack folder with:
+
+    git submodule update # syncs submodule rack folder with what parent project has as commits
+
+## More Details
+
+The rest of the guide will explain in a little more detail submodules.
+
+## What are Git Submodules?
+
+Git submodules are a way to have a subfolder in your project be managed as a separate git repo.  The submodule folder is its own separate git repo and has its own history. The parent git project references a commit from the submodule project to sync up the subfolder accordingly.  Using submodules allows you to include a rack subfolder project into your Jets project code base and managed the rack project as a separate git repo.
+
+By using the `--submodule` option when you run the `jets import` command, Jets imports the rack project to the rack folder as a submodule.  This allows you to keep development of the rack project independent from the development of the Jets project. This is a useful setup if you are testing [Jets Mega Mode](http://rubyonjets.com/docs/megamode/) for more extended periods of time.
+
+We'll show you how to managed and sync the `rack` submodule folder with the parent Jets project folder.
+
+### rack submodule
+
+A rack folder was added to your Jets project as a git submodule.  Essentially this command was run.
+
+    git submodule add --force <%= @rack_repo_url %> rack
+
+The rack submodule folder gets immediately synced as a part of that `git submodule add` command.  This has already happened as part of the `jets <%= @import_command %>, we're just explaining the underlying command in case you're interested.
+
+### Fresh Clone
+
+**IMPORTANT**: On a fresh clone of your project, submodule folders do not automatically update and appear "empty".  This can be confusing for people who don't use submodules often. So here are the commands to update and sync the submodule folder:
+
+    git clone <%= @jets_project_repo_url %>
+    git submodule init # important to run init or next update will do nothing
+    git submodule update # after this the rack folder will no longer be empty
+                         # and will have code from <%= @rack_repo_url %>
+
+### Remove submodule
+
+If you ever decide to remove the submodule from your project, here are the commands.
+
+    git submodule deinit rack
+    git rm rack
+    # then add and commit your changes
+
+## Updating Projects
+
+The typical workflow is to go into the rack folder and run `git pull` to update the submodule folder to the latest changes. Then you cd back up to the main Jets project folder and run `git add`.  This updates the project submodule commit reference, which then allows others to pull down the changes and resync the submodules to the same commit. We'll go through some examples to help explain:
+
+### Updating rack folder submodule
+
+Here's an example where we will update the rack submodule folder to the latest `master` branch. Remember the master branch refers to the `rack` submodule folder of the <%= @rack_repo_url %> in this case.
+
+    cd my-jets-project # root of the Jets project
+    cd rack # in the submodule now, which contains a different repo history
+    git checkout master # on a fresh clone, the submodule folder will point to a specific git sha instead of a branch
+    git pull # get latest changes in master
+    cd .. # back to parent Jets project
+    git status # notice, it'll say: modified:  rack (new commits)
+    git add rack # updates the main projects' reference to the submodule git commit
+    git commit -m "update rack submodule"
+    git push # send your changes to everyone else
+
+Eventually, later another developer will pull down your changes on the Jets project and notice that the submodules have been updated.  When he runs a `git pull` and then does a `git status` he'll notice this:
+
+    $ git pull # another developer pulled down the changes
+    $ git st # notice the changes
+        modified:   rack (new commits)
+    $ git diff # another way a summary of the changes in the rack project
+    Submodule rack 6b0fb3a..4f6ea3f (rewind):
+      < test commit in rack submodule project
+
+This is when the developer will need to resync the rack submodule folder. He does it with this:
+
+    git submodule update # updates the rack folder to the commit that the parent is referencing
+
+That's it!