jets 0.5.3 → 0.5.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2b8471d0065ecdd475bc5aa957e80691f71a7754a5cbb7aad66f30b559ee4fc3
-  data.tar.gz: 196bcb78a37694d17849d9ee16153bb39f7ceb85a1e5d3e9eece9499125cbe13
+  metadata.gz: 05f493298a24d9f81047427851d58c6a2b07d210c1712e92bbe7f75b26d17933
+  data.tar.gz: daaa2abacea4002f91a0d4a9d49085c25618b3d6ce7df00c856a04aa6b13d9f5
 SHA512:
-  metadata.gz: c922aa0f644d331e387f448673da9bc674fa9b78095646a686a815f557ee34d6525f3ea186a35b3f04ca51caab699352a86aac7fa7a15e7a7124676c1b2105a3
-  data.tar.gz: 3973fc0339e6f8a7d2a1d720df63024e9ad7be143ae82e5c78ebd0970a3e50d0e23cababcae79795eed6c449683e30704d26bbc44349c216ee21e276f1ea0364
+  metadata.gz: 76f11fd73231957fb357babf695267f5bf37b955fa2d9bcc916979412dc07315a37027dbab1f0a252dc5b3f6017f2aaf2216797090420ab5ad414c3e0a441319
+  data.tar.gz: 625f09d4db4790fd7765031932f16f67adc8b116d2e7b07a1972962f6319d46a887b2bcb36dbc7cbe00fafc29b3628913e281b55335c4456ffaacb5096de22ed

data/CHANGELOG.md

@@ -3,6 +3,13 @@
 All notable changes to this project will be documented in this file.
 This project *tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
 
+## [0.5.4]
+- add route check before cloudformation update: pull request #11
+- hide confusing debugging logs for node shim for user
+- update docs, grammar fixes
+- update initial welcome page, improve mobile, use encoding: utf-8 for starter index page
+- update to use Jets::RUBY_VERSION
+
 ## [0.5.3]
 - add x-jets-prewarm-count and x-jets-call-count headers: pull request #10 from tongueroo/call-count
 - adjust default prewarming concurrency to 2
@@ -19,7 +26,7 @@ This project *tries* to adhere to [Semantic Versioning](http://semver.org/), eve
 - update docs
 
 ## [0.5.0]
-- First good release
+- First big good release
 
 ## [0.1.2]
 - Fix bundled gems.

data/Gemfile.lock

@@ -11,7 +11,7 @@ GIT
 PATH
   remote: .
   specs:
-    jets (0.5.3)
+    jets (0.5.4)
       actionpack
       actionview
       activerecord

data/README.md

@@ -9,7 +9,7 @@ Ruby and Lambda splat out a baby and that child's name is Jets.
 
 ## What is Jets?
 
-Jets is a Ruby Serverless Framework.  Jets allows you to create serverless applications with a beautiful language: Ruby.  It includes everything required to build an application and deploy it to on AWS Lambda.
+Jets is a Ruby Serverless Framework.  Jets allows you to create serverless applications with a beautiful language: Ruby.  It includes everything required to build an application and deploy it to AWS Lambda.
 
 It is key to understand AWS Lambda and API Gateway to understand Jets conceptually.  Jets maps your code to Lambda functions and API Gateway resources.
 
@@ -123,14 +123,5 @@ For more documentation, check out the official docs: [Ruby on Jets](http://rubyo
 * [Prewarming](http://rubyonjets.com/docs/prewarming/)
 * [Installation](http://rubyonjets.com/docs/install/)
 * [CLI Reference](http://rubyonjets.com/reference/)
-
-## Contributing
-
-I love pull requests! Happy to answer questions to help.
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
-
+* [Contributing](http://rubyonjets.com/docs/contributing/)
+* [Support Jets](http://rubyonjets.com/support-jets/)

data/lib/jets.rb

@@ -9,6 +9,9 @@ require "pp" # TODO: remove pp after debugging
 require "memoist"
 
 module Jets
+  # When we update Jets::RUBY_VERSION, need to update lambdagem/base.rb: def jets_ruby_version also
+  RUBY_VERSION = "2.5.0"
+
   autoload :CLI, "jets/cli"
   autoload :Commands, "jets/commands"
 

data/lib/jets/builders/code_builder.rb

@@ -51,11 +51,8 @@ require "action_view"
 class Jets::Builders
   class CodeBuilder
     include Jets::Timing
-    # When we update JETS_RUBY_VERSION, need to update `def jets_ruby_version` in
-    # vendor/lambdagem/lib/lambdagem/base.rb also.
-    JETS_RUBY_VERSION = "2.5.0"
-
     include ActionView::Helpers::NumberHelper # number_to_human_size
+
     attr_reader :full_project_path
     def initialize
       # Expanding to the full path and capture now.
@@ -118,12 +115,12 @@ class Jets::Builders
 
     def extract_ruby
       headline "Setting up a vendored copy of ruby."
-      Lambdagem::Extract::Ruby.new(JETS_RUBY_VERSION, lambdagem_options).run
+      Lambdagem::Extract::Ruby.new(Jets::RUBY_VERSION, lambdagem_options).run
     end
 
     def extract_gems
       headline "Replacing compiled gems with AWS Lambda Linux compiled versions."
-      GemReplacer.new(JETS_RUBY_VERSION, lambdagem_options).run
+      GemReplacer.new(Jets::RUBY_VERSION, lambdagem_options).run
     end
 
     # This happens in the current app directory not the tmp app_root for simplicity
@@ -222,7 +219,7 @@ class Jets::Builders
     # The lambda server only has ruby 2.5.0 installed.
     def reconfigure_ruby_version
       ruby_version = "#{full(tmp_app_root)}/.ruby-version"
-      IO.write(ruby_version, JETS_RUBY_VERSION)
+      IO.write(ruby_version, Jets::RUBY_VERSION)
     end
 
     def copy_bundled_to_app_root
@@ -383,8 +380,8 @@ EOL
     def check_ruby_version
       unless ruby_version_supported?
         puts "You are using ruby version #{RUBY_VERSION} which is not supported by Jets."
-        ruby_variant = JETS_RUBY_VERSION.split('.')[0..1].join('.') + '.x'
-        abort("Jets uses ruby #{JETS_RUBY_VERSION}.  You should use a variant of ruby #{ruby_variant}".colorize(:red))
+        ruby_variant = Jets::RUBY_VERSION.split('.')[0..1].join('.') + '.x'
+        abort("Jets uses ruby #{Jets::RUBY_VERSION}.  You should use a variant of ruby #{ruby_variant}".colorize(:red))
       end
     end
 
@@ -392,7 +389,7 @@ EOL
       pattern = /(\d+)\.(\d+)\.(\d+)/
       md = RUBY_VERSION.match(pattern)
       ruby = {major: md[1], minor: md[2]}
-      md = JETS_RUBY_VERSION.match(pattern)
+      md = Jets::RUBY_VERSION.match(pattern)
       jets = {major: md[1], minor: md[2]}
 
       ruby[:major] == jets[:major] && ruby[:minor] == jets[:minor]

data/lib/jets/builders/gem_replacer.rb

@@ -1,6 +1,6 @@
 # def extract_gems
 #   headline "Replacing compiled gems with Lambda Linux versions."
-#   Lambdagem::Extract::Gem.new(JETS_RUBY_VERSION,
+#   Lambdagem::Extract::Gem.new(Jets::RUBY_VERSION,
 #     s3: "lambdagems",
 #     dest: full(cache_area),
 #   ).run

data/lib/jets/builders/node-shim.js

@@ -5,6 +5,7 @@ const fs = require('fs');
 const TMP_LOG_PATH = '/tmp/shim-subprocess.log';
 const subprocess_out = fs.openSync(TMP_LOG_PATH, 'a');
 const subprocess_err = fs.openSync(TMP_LOG_PATH, 'a');
+const JETS_DEBUG = process.env.JETS_DEBUG // set JETS_DEBUG=1 to see more debugging info
 
 function once() {
   // Uncomment fake run once locally. No need to do this on real lambda environment.
@@ -67,8 +68,14 @@ function rubyError(resp) {
 // But locally when we're testing the shim, the log output can mess up piping
 // to jq. So not logging to stdout because when testing this shim locally the
 // stdout output messes up a pipe to jq.
-function log(text) {
-  console.error(text);
+function log(text, level="info") {
+  if (level == "info" && JETS_DEBUG) {
+    // only log if JETS_DEBUG is set
+    console.error(text);
+  } else if (level == "debug") {
+    // always log if "debug" passed into method
+    console.error(text);
+  }
 }
 
 ////////////////////////////

data/lib/jets/commands/deploy.rb

@@ -13,6 +13,8 @@ module Jets::Commands
       return if @options[:noop]
 
       build_code
+      validate_routes!
+
       # first time will deploy minimal stack
       exit_unless_updateable!
 
@@ -27,6 +29,18 @@ module Jets::Commands
     end
     time :build_code
 
+    # Checks that all routes are validate and have corresponding lambda functions
+    def validate_routes!
+      return if Jets::Router.all_routes_valid
+
+      puts "Deploy fail: The jets application contain invalid routes.".colorize(:red)
+      puts "Please double check the routes below map to valid controllers:"
+      Jets::Router.invalid_routes.each do |route|
+        puts "  /#{route.path} => #{route.controller_name}##{route.action_name}"
+      end
+      exit 1
+    end
+
     def ship(stack_options)
       options = @options.merge(stack_options) # includes stack_type and s3_bucket
       Jets::Commands::Build.new(options).build_templates

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

@@ -1 +1,8 @@
-Generates a node shim and bundles a Linux Ruby in the bundled folder.  Creates a zip file to be uploaded to Lambda for each handler. This allows you to build the project and inspect the zip file that gets deployed to AWS Lambda.
+Builds a zip file package to be uploaded to AWS Lambda. This allows you to build the project without deploying and inspect the zip file that gets deployed to AWS Lambda. The package contains:
+
+* your application code
+* generated node shims
+* bundled gems
+* bundled Ruby
+
+If the application has no ruby code and only uses polymorphic functions, then gems and Ruby is not bundled up.

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

@@ -1,10 +1,16 @@
+## Remote mode
+
 Invoke the lambda function on AWS. The `jets call` command does a few extra things for your convenience:
 
 It adds the function namespace to the function name.  So, you pass in `posts_controller-index` and the Lambda function is `demo-dev-posts_controller-index`.
 
-It can print out the last 4KB of the lambda logs with the `--show-logs` option. The logging output is directed to stderr.  The response output from the lambda function itself is directed to stdout.  This is done so you can safely pipe the results of the call command to other tools like jq.
+CLI Name | Lambda Function
+--- | ---
+posts_controller-index | demo-dev-posts_controller-index
+
+The `jets call` command can also print out the last 4KB of the lambda logs with the `--show-logs` option. The logging output is directed to stderr and the response output from the lambda function itself is directed to stdout so you can safely pipe the results of the call command to other tools like `jq`.
 
-For controllers, the event you pass at the CLI is automatically transformed into Lambda Proxy payload that contains the params as the queryStringParameters.  For example:
+For [controllers](http://rubyonjets.com/docs/controllers/), the event you pass at the CLI is automatically transformed into [Lambda Proxy](https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html) payload that contains the params as the `queryStringParameters`.  For example:
 
     {"test":1}
 
@@ -12,11 +18,11 @@ Gets changed to:
 
     {"queryStringParameters":{"test":1}}
 
-This spares you from assembling the event payload manually to the payload that Jets controllers normally recieve.  If you would like to disable this Lambda Proxy transformation then use the `--no-lambda-proxy` flag.
+This spares you from assembling the event payload manually to the payload that Jets controllers normally receive.  If you would like to disable this Lambda Proxy transformation then use the `--no-lambda-proxy` flag.
 
-For jobs, the event is passed through untouched.
+For [jobs](http://rubyonjets.com/docs/jobs/), the event is passed through untouched.
 
-Examples:
+## Examples
 
     jets call hard_job-drive '{"test":1}'
     jets call hard_job-drive '{"test":1}' | jq .
@@ -33,7 +39,7 @@ The equivalent AWS Lambda CLI command:
     aws lambda invoke --function-name demo-dev-posts_controller-index --payload '{"queryStringParameters":{"test":1}}' outfile.txt
     cat outfile.txt | jq '.'
 
-For convenience, you can also provide the function name with only dashes and jets call will gets what function you intend to call. Examples:
+For convenience, you can also provide the function name with only dashes and `jets call` figures out what function you intend to call. Examples:
 
     jets call posts-controller-index
     jets call admin-related-pages-controller-index
@@ -43,13 +49,13 @@ Are the same as:
     aws lambda invoke --function-name demo-dev-posts_controller-index
     aws lambda invoke --function-name demo-dev-admin/related_pages_controller-index
 
-In order to allow calling functions with all dashes, the call method evaluates the app code and finds if the controller and method actually exists.  If you want to turn this off and want to always explicitly provide the method name use the `--no-guess` option.  The function name will then have to match the lambda function without the namespace. Example:
+Jets figures out what functions to call by evaluating the app code and finds if the controller and method exists.  If you want to turn guess mode off and want to always explicitly provide the method name use the `--no-guess` option.  The function name will then have to match the lambda function without the namespace. Example:
 
     jets call admin-related_pages_controller-index --no-guess
 
-Local mode:
+## Local mode
 
-Instead of calling AWS lambda remote, you can also have `jets call` use the code directly on your machine.  To enable this use the `--local` flag. Example:
+Instead of calling AWS lambda remote, you can also have `jets call` use the code directly on your machine.  To enable this, use the `--local` flag. Example:
 
     jets call hard_job-drive --local
 

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

@@ -1,4 +1,10 @@
 ## Example
 
     $ jets console
-    > Post.find("myid")
+    >> Post.table_name
+    => "posts"
+    >> ActiveRecord::Base.connection.tables
+    => ["schema_migrations", "ar_internal_metadata", "posts"]
+    >> Jets.env
+    => "development"
+    >>

data/lib/jets/commands/help/db/generate.md

@@ -5,4 +5,4 @@ Generates migration in `db/migrate`
     jets db:generate create_articles title:string user_id:integer
     jets db:generate AddTitleBodyToPost title:string body:text published:boolean
 
-This task delegates to Rails `rails generate migration`.  For more examples: `rails generate migration -h`.
+This task delegates to Rails `rails generate migration`.  For more examples, refer to the [Active Record Migrations Rails Guide](https://edgeguides.rubyonrails.org/active_record_migrations.html).

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

@@ -2,4 +2,8 @@ This is like running the psql command with the `config/database.yml` values and
 
 ## Example
 
-    jets dbconsole
+    $ jets dbconsole
+    psql (9.2.24)
+    Type "help" for help.
+
+    demo_dev=>

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

@@ -1,8 +1,21 @@
-This essentially deletes the associated CloudFormation stacks.
+This deletes the all the contents in the internal s3 bucket that jets uses and the associated CloudFormation stacks.
 
 ## Examples
 
     $ jets delete
+    Deleting project...
+    Are you sure you want to want to delete the 'demo-dev' project? (y/N)
+    y
+    First, deleting objects in s3 bucket demo-dev-s3bucket-89jrrj60c7bj
+    Deleting demo-dev...
+    05:14:09AM DELETE_IN_PROGRESS AWS::CloudFormation::Stack demo-dev User Initiated
+    ...
+    05:14:23AM DELETE_IN_PROGRESS AWS::CloudFormation::Stack PostsController
+    05:15:31AM DELETE_COMPLETE AWS::S3::Bucket S3Bucket
+    Stack demo-dev deleted.
+    Time took for deletion: 1m 27s.
+    Project demo-dev deleted!
+    $
 
 You can bypass the are you sure prompt with the `--sure` flag.
 

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

@@ -1,5 +1,32 @@
-This packages up the project and deploys it AWS Lambda. This essentially updating the CloudFormation stack.
+This builds the project and deploys it AWS Lambda. The deployment is mainly handled by CloudFormation.  To check on the status of the deploy you can also check the CloudFormation console.
+
+![](http://rubyonjets.com/img/cli/deploy-cloudformation-status.png)
 
 ## Example
 
     $ jets deploy
+    Deploying to Lambda demo-dev environment...
+    => Compling assets in current project directory
+    => Copying current project directory to temporary build area: /tmp/jets/demo/app_root
+    => Tidying project: removing ignored files to reduce package size.
+    => Generating node shims in the handlers folder.
+    => Bundling: running bundle install in cache area: /tmp/jets/demo/cache.
+    => Setting up a vendored copy of ruby.
+    => Replacing compiled gems with AWS Lambda Linux compiled versions.
+    Creating zip file.
+    => cd /tmp/jets/demo/app_root && zip --symlinks -rq /tmp/jets/demo/code/code-temp.zip .
+    Building parent template.
+    Deploying CloudFormation stack with jets app!
+    Uploading /tmp/jets/demo/code/code-7169d0ac.zip (88.8 MB) to S3
+    Time to upload code to s3: 1s
+    Deploying CloudFormation stack with jets app!
+    02:08:20AM UPDATE_IN_PROGRESS AWS::CloudFormation::Stack demo-dev User Initiated
+    02:08:23AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiGateway
+    ...
+    02:08:48AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack PostsController
+    02:10:03AM UPDATE_COMPLETE AWS::CloudFormation::Stack demo-dev
+    Stack success status: UPDATE_COMPLETE
+    Time took for stack deployment: 1m 46s.
+    Prewarming application...
+    API Gateway Endpoint: https://ewwnealfk0.execute-api.us-west-2.amazonaws.com/dev/
+    $

data/lib/jets/commands/help/dynamodb/generate.md

@@ -1,27 +1,29 @@
-Generates a migration file which can be used to create a DynamoDB table.  To run the migration file use `jets db:migrate`.
+Generates a migration file which can be used to create a DynamoDB table.  To run the migration file use `jets dynamodb:migrate`.
 
-The table name will have a namespace. For example, given your project is called `proj`, the env is called `dev`, and you create a table called `posts`.  The DynamoDB full table name will be `demo-dev-posts`.  You can change this behavior by editing your `config/dynamodb.yml`.
+The table name will have a namespace. For example, if your project is called `demo`, the environment is `development`, and you create a table called `posts`.  The DynamoDB full table name will be `demo-dev-posts`.  You can change this behavior by editing your `config/dynamodb.yml` and adjusting the `table_namespace` value.
 
-For the `--partition-key` option, DynamoDB tables support certain types of attribute types. The cli will parse the --partition-key option and use the second part of the option to map it to the underlying DynamoDB type using this mapping.
+DynamoDB tables support certain types of attribute types. The CLI will parse the `--partition-key` option and use the second part of the option to map it to the underlying DynamoDB type using this mapping.
 
-  ATTRIBUTE_TYPE_MAP = {
-    'string' => 'S',
-    'number' => 'N',
-    'binary' => 'B',
-    's' => 'S',
-    'n' => 'N',
-    'b' => 'B',
-  }
+```ruby
+ATTRIBUTE_TYPE_MAP = {
+  'string' => 'S',
+  'number' => 'N',
+  'binary' => 'B',
+  's' => 'S',
+  'n' => 'N',
+  'b' => 'B',
+}
+```
 
-For example, --partition-key id:string will map 'string' to 's'.  More info available at the ruby aws-sdk docs: [Aws::DynamoDB::Types::AttributeDefinition](https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/DynamoDB/Types/AttributeDefinition.html)
+For example, `--partition-key id:string`  maps 'string' to 's'.  More info on DynamoDB types is available at the ruby aws-sdk docs: [Aws::DynamoDB::Types::AttributeDefinition](https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/DynamoDB/Types/AttributeDefinition.html)
 
-Examples:
+## Examples
 
     $ jets dynamodb:generate create_posts --partition-key id # default attribute type is string
     $ jets dynamodb:generate create_posts --partition-key id:number # attribute type will be number
     $ jets dynamodb:generate create_comments --partition-key post_id:string --sort-key created_at:string
 
-To run migrations:
+## Running migrations
 
     $ jets dynamodb:migrate path/to/migration
     $ jets dynamodb:migrate dynamodb/migrate/20171112162404-create_articles_migration.rb
@@ -34,14 +36,14 @@ To run:
 
     $ jets dynamodb:migrate dynamodb/migrate/20171112161530-create_posts_migration.rb
 
-Conventions:
+## Conventions
 
-An create_table or update_table migration file is generated based name you provide.  If update is found in the name then an update_table migration table is generated.
+A create_table or update_table migration file is generated based name you provide.  If `update` is included in the name then an update_table migration table is generated. If `create` is included in the name then a create_table migration table is generated.
 
 The table_name is also inferred from the migration name you provide.  Examples:
 
-    $ jets dynamodb:generate create_posts => table_name: posts
-    $ jets dynamodb:generate update_comments => table_name: comments
+    $ jets dynamodb:generate create_posts # table_name: posts
+    $ jets dynamodb:generate update_comments # table_name: comments
 
 You can override both of these conventions:
 

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

@@ -1,5 +1,22 @@
-This piggy backs off of rails generators.
+This piggy backs off of the [rails scaffold generator](https://guides.rubyonrails.org/command_line.html#rails-generate).
 
 ## Example
 
-    jets generate scaffold Post title:string body:text published:boolean
+    $ jets generate scaffold Post title:string body:text published:boolean
+          invoke  active_record
+          create    db/migrate/20180817052529_create_posts.rb
+          create    app/models/post.rb
+          invoke  resource_route
+           route    resources :posts
+          invoke  scaffold_controller
+          create    app/controllers/posts_controller.rb
+          invoke    erb
+          create      app/views/posts
+          create      app/views/posts/index.html.erb
+          create      app/views/posts/edit.html.erb
+          create      app/views/posts/show.html.erb
+          create      app/views/posts/new.html.erb
+          create      app/views/posts/_form.html.erb
+          invoke    helper
+          create      app/helpers/posts_helper.rb
+    $

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

@@ -1,9 +1,29 @@
 ## Examples
 
-    $ jets new blog
+    $ jets new demo
+    Creating new project called demo.
+          create  demo/app/controllers/application_controller.rb
+          create  demo/app/helpers/application_helper.rb
+          create  demo/app/jobs/application_job.rb
+    ...
+    ================================================================
+    Congrats  You have successfully created a Jets project.
+
+    Cd into the project directory:
+      cd demo
+
+    To start a server and test locally:
+      jets server # localhost:8888 should have the Jets welcome page
+
+    Scaffold example:
+      jets generate scaffold Post title:string body:text published:boolean
+
+    To deploy to AWS Lambda:
+      jets deploy
+    $
 
 Use the `--repo` flag to clone an example project from GitHub instead.  With this flag, jets new command clones a jets project repo from GitHub:
 
     $ jets new blog --repo tongueroo/tutorial
-    $ jets new blog --repo tongueroo/todos
-    $ jets new blog --repo user/repo # any github repo
+    $ jets new todos --repo tongueroo/todos
+    $ jets new whatever --repo user/repo # any github repo

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

@@ -1,3 +1,17 @@
 ## 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       |
+    | GET    |                | jets/welcome#index |
+    | ANY    | *catchall      | jets/public#show   |
+    +--------+----------------+--------------------+
+    $

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

@@ -3,4 +3,13 @@ The local server for mimics API Gateway and provides a way to test your app loca
 ## Examples
 
     $ jets server
-    $ jets server --host 0.0.0.0
+    => 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

@@ -1 +1,14 @@
-Essentially the events of the CloudFormation stack update. If the CloudFormation stack is currently updating, this will tail the events logs.
+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/url.md

@@ -1,5 +1,6 @@
-Provides the app url if routes have been configured.
+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/main.rb

@@ -84,7 +84,7 @@ module Jets::Commands
       Jets::Generator.invoke(generator, *args)
     end
 
-    desc "status", "Shows the current status of the Jets app."
+    desc "status", "Shows the current status of the Jets app"
     long_desc Help.text(:status)
     def status
       Jets::Cfn::Status.new(options).run

data/lib/jets/commands/templates/skeleton/public/index.html.tt

@@ -1,3 +1,4 @@
+# encoding: utf-8
 <!DOCTYPE html>
 <html>
 <head>
@@ -32,6 +33,11 @@
     .title {
       font-size: 1.5em;
     }
+    @media (max-width: 500px) {
+      .title {
+        font-size: 1.3em;
+      }
+    }
     .intro {
       text-align: left;
       font-size: large;
@@ -48,6 +54,12 @@
       width: 99%;
       overflow: auto;
     }
+    @media (max-width: 500px) {
+      pre {
+        margin-left: -30px;
+        font-size: 0.8em;
+      }
+    }
   </style>
 </head>
 
@@ -55,7 +67,7 @@
   <div class="container">
     <header class="header">
       <img src="https://s3.amazonaws.com/jets-public/jets/images/jets.png" class="logo" alt="logo" />
-      <h1 class="title">Welcome. Congrats on setting up Jets.</h1>
+      <h1 class="title">Welcome and congrats 🎉<br /> Jets is running.</h1>
     </header>
     <div class="intro">
       <p>
@@ -68,11 +80,12 @@
         $ open http://localhost:8888/posts
         $ jets help
       </code></pre></div>
-      <p>More on: <a href="http://rubyonjets.com">rubyonjets.com</a></p>
+      <p>More on info: <a href="http://rubyonjets.com">rubyonjets.com</a></p>
+      <p>Also check out the <a href="http://rubyonjets.com/reference">Jets CLI reference</a>.</p>
     </div>
     <p class="version">
       <strong>Jets version:</strong> <%= Jets.version %><br />
-      <strong>Ruby version:</strong> <%= RUBY_VERSION %> (<%= RUBY_PLATFORM %>)
+      <strong>Ruby version:</strong> <%= Jets::RUBY_VERSION %>
     </p>
   </div>
 </body>

data/lib/jets/route.rb

@@ -48,6 +48,17 @@ class Jets::Route
     to.sub(/.*#/,'')
   end
 
+  # Checks to see if the corresponding controller exists. Useful to validate routes
+  # before deploying to CloudFormation and then rolling back.
+  def valid?
+    controller_class = begin
+      controller_name.constantize
+    rescue NameError
+      return false
+    end
+    controller_class.all_tasks.keys.include?(action_name.to_sym)
+  end
+
   # Extracts the path parameters from the actual path
   # Only supports extracting 1 parameter. So:
   #

data/lib/jets/router.rb

@@ -111,5 +111,13 @@ module Jets
       end
       table
     end
+
+    def self.all_routes_valid
+      invalid_routes.empty?
+    end
+
+    def self.invalid_routes
+      routes.select { |r| !r.valid? }
+    end
   end
 end

data/lib/jets/ruby_server.rb

@@ -43,7 +43,7 @@ module Jets
     def serve
       # child process
       server = TCPServer.new(8080) # Server bind to port 8080
-      puts "TCPServer started on port #{PORT}"
+      puts "Ruby server started on port #{PORT}"
       input_completed = false
       loop do
         event, handler = nil, nil

data/lib/jets/version.rb

@@ -1,3 +1,3 @@
 module Jets
-  VERSION = "0.5.3"
+  VERSION = "0.5.4"
 end

data/vendor/lambdagem/lib/lambdagem/base.rb

@@ -10,7 +10,7 @@ class Lambdagem::Base
     @build_root = options[:build_root] || "/tmp/lambdagem"
     @artifacts_root = "#{@build_root}/artifacts"
     @s3_bucket = options[:s3] || 'lambdagems'
-    @lambdagems_url = options[:lambdagems_url] || "https://lambdagems.com"
+    @lambdagems_url = options[:lambdagems_url] || "https://gems.lambdagems.com"
   end
 
   # The gems are stored in a ruby version folder that always has a patch version of

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jets
 version: !ruby/object:Gem::Version
-  version: 0.5.3
+  version: 0.5.4
 platform: ruby
 authors:
 - Tung Nguyen
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-08-16 00:00:00.000000000 Z
+date: 2018-08-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -472,10 +472,6 @@ files:
 - lib/jets/commands/help/dynamodb/migrate.md
 - lib/jets/commands/help/generate.md
 - lib/jets/commands/help/new.md
-- lib/jets/commands/help/process/controller.md
-- lib/jets/commands/help/process/function.md
-- lib/jets/commands/help/process/job.md
-- lib/jets/commands/help/process/rule.md
 - lib/jets/commands/help/routes.md
 - lib/jets/commands/help/server.md
 - lib/jets/commands/help/status.md

data/lib/jets/commands/help/process/controller.md

@@ -1,6 +0,0 @@
-The node shim spawns out to this command.
-
-## Example
-
-    $ jets process:controller '{"pathParameters":{}}' '{"context":"data"}' "handlers/controllers/posts_controller.index"
-    $ jets process:controller '{"pathParameters":{"id":"tung"}}' '{}' handlers/controllers/posts_controller.show

data/lib/jets/commands/help/process/function.md

@@ -1,5 +0,0 @@
-The node shim spawns out to this command.
-
-## Example
-
-    $ jets process function '{"key1":"value1"}' '{}' "handlers/function/hello.world"

data/lib/jets/commands/help/process/job.md

@@ -1,5 +0,0 @@
-The node shim spawns out to this command.
-
-## Example
-
-    $ jets process:job '{"we":"love", "using":"Lambda"}' '{"context":"data"}' "handlers/jobs/hard_job.dig"

data/lib/jets/commands/help/process/rule.md

@@ -1,5 +0,0 @@
-The node shim spawns out to this command.
-
-## Example
-
-    $ jets process:rule file://config_change.json '{"context":"data"}' "handlers/rules/game_rule.protect"