jets.benforeva 3.0.17.pre.mount.pre.fix

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: dd3345ba501b9a24cf928955ceedbe5d701367b4b54ba66e6ec7827f3941b05a
+  data.tar.gz: a8260846991ee412205ddf87ab7020303c6907c4147385b6dcb83f326d069477
+SHA512:
+  metadata.gz: 046625d48125fc47a9cf9c3ac9d3fe40f0fd1e4f25f359ce249fdcc32d74639d8f4ea08592631c33fd97e77e36c1500e0c64a76552a6b856d8bbaf9e406d61e0
+  data.tar.gz: b75c95125611471f8c5537dae0f0b94931cbff88611a958ad8febed8018a478a487e7caf93efcf862f9062701441e5e1ecbc0e93c0c7da85571f9a498145e7e4

data/.circleci/config.yml

@@ -0,0 +1,92 @@
+# Ruby CircleCI 2.0 configuration file
+#
+# Check https://circleci.com/docs/2.0/language-ruby/ for more details
+#
+version: 2
+jobs:
+  build:
+    docker:
+      # specify the version you desire here
+      - image: circleci/ruby:2.5.0-node-browsers
+
+      # Specify service dependencies here if necessary
+      # CircleCI maintains a library of pre-built images
+      # documented at https://circleci.com/docs/2.0/circleci-images/
+      # - image: circleci/postgres:9.4
+
+    working_directory: ~/repo
+
+    steps:
+      - checkout
+
+      - run:
+          name: submodule sync
+          command: |
+            git submodule sync
+            git submodule update --init
+
+      # Download and cache dependencies
+      - restore_cache:
+          keys:
+          - v2-dependencies-{{ checksum "jets.gemspec" }}
+          # fallback to using the latest cache if no exact match is found
+          - v2-dependencies-
+
+      - run:
+          name: install dependencies
+          command: |
+            bundle install --jobs=4 --retry=3 --path vendor/bundle
+
+      - save_cache:
+          paths:
+            - ./vendor/bundle
+          key: v2-dependencies-{{ checksum "jets.gemspec" }}
+
+      # Database setup
+      # - run: bundle exec rake db:create
+      # - run: bundle exec rake db:schema:load
+
+      - run:
+          name: install dynamodb-local
+          command: |
+            whoami > /tmp/whoami.txt
+
+            mkdir ~/dynamodb_local_latest
+            cd ~/dynamodb_local_latest
+            wget https://s3-us-west-2.amazonaws.com/dynamodb-local/dynamodb_local_latest.tar.gz
+            tar zxf dynamodb_local_latest.tar.gz
+            cat >~/dynamodb-local <<EOL
+            #!/bin/sh
+            exec java -Djava.library.path=~/dynamodb_local_latest/DynamoDBLocal_lib -jar ~/dynamodb_local_latest/DynamoDBLocal.jar -sharedDb
+            EOL
+
+            chmod a+x ~/dynamodb-local
+            sudo mv ~/dynamodb-local /usr/local/bin/dynamodb-local
+
+      - run:
+          name: start dynamodb-local
+          command: dynamodb-local
+          background: true
+
+      # run tests!
+      - run:
+          name: run tests
+          command: |
+            mkdir /tmp/test-results
+
+            cat >.rspec <<EOL
+            --format documentation
+            --exclude-pattern spec/fixtures/apps/**/*
+            --format RspecJunitFormatter \
+            --out /tmp/test-results/rspec.xml \
+            --require spec_helper
+            EOL
+
+            bundle exec rspec
+
+      # collect reports
+      - store_test_results:
+          path: /tmp/test-results
+      - store_artifacts:
+          path: /tmp/test-results
+          destination: test-results

data/.cody/README.md

@@ -0,0 +1,13 @@
+## Update Project
+
+To update the CodeBuild project:
+
+Main services:
+
+    AWS_PROFILE=bolt-oss cody deploy jets --type docs # mainly cli docs and subnav update
+
+## Start a Deploy
+
+To start a CodeBuild build which kicks off a deploy:
+
+    AWS_PROFILE=bolt-oss cody start jets --type docs

data/.cody/docs/bin/build.sh

@@ -0,0 +1,7 @@
+#!/bin/bash -eux
+
+.cody/docs/bin/git_setup.sh
+.cody/docs/bin/bundler_setup.sh
+.cody/docs/bin/cli_docs.sh
+.cody/docs/bin/subnav.sh
+.cody/docs/bin/git_commit.sh

data/.cody/docs/bin/bundler_setup.sh

@@ -0,0 +1,8 @@
+#!/bin/bash -eux
+
+# This Docker image needs bundler 1.16.6 installed
+gem install bundler:1.16.6
+echo $BUNDLER_VERSION
+
+# Generate docs
+gem update --system

data/.cody/docs/bin/cli_docs.sh

@@ -0,0 +1,6 @@
+#!/bin/bash -eux
+
+# Unsure why but setting BUNDLE_GEMFILE fixes build in the codebuild docker env
+export BUNDLE_GEMFILE=$(pwd)/Gemfile
+bundle
+rake docs

data/.cody/docs/bin/git_commit.sh

@@ -0,0 +1,27 @@
+#!/bin/bash -eux
+
+out=$(git status docs)
+if [[ "$out" = *"nothing to commit"* ]]; then
+  exit
+fi
+
+COMMIT_MESSAGE="docs updated by codebuild"
+
+# If the last commit already updated the docs, then exit.
+# Preventable measure to avoid infinite loop.
+if git log -1 --pretty=oneline | grep "$COMMIT_MESSAGE" ; then
+  exit
+fi
+
+# If reach here, we have some changes on docs that we should commit.
+git add docs
+git commit -m "$COMMIT_MESSAGE"
+
+# SSH_KEY_S3_PATH set as codebuild environment variable
+aws s3 cp $SSH_KEY_S3_PATH ~/.ssh/id_rsa
+chmod 400 ~/.ssh/id_rsa
+sed -i -- 's|https://github.com/|git@github.com:|g' .git/config
+
+# https://makandracards.com/makandra/12107-git-show-current-branch-name-only
+current_branch=$(git rev-parse --abbrev-ref HEAD)
+git push origin "$current_branch"

data/.cody/docs/bin/git_setup.sh

@@ -0,0 +1,12 @@
+#!/bin/bash -eux
+
+# git push:
+#   CODEBUILD_WEBHOOK_HEAD_REF=refs/heads/codebuild
+#   CODEBUILD_WEBHOOK_TRIGGER=branch/codebuild
+#   CODEBUILD_SOURCE_VERSION=f0eb542 # resolved sha
+# cb start:
+#   CODEBUILD_SOURCE_VERSION=codebuild
+
+git config --global user.email "tongueroo@gmail.com"
+git config --global user.name "Tung Nguyen"
+

data/.cody/docs/bin/subnav.sh

@@ -0,0 +1,14 @@
+#!/bin/bash -eux
+
+cd docs
+# Unsure why but if cli_docs.sh runs bundle first, then bundle wont use the right bundler file
+export BUNDLE_GEMFILE=$(pwd)/Gemfile
+bundle
+bundle exec jekyll serve --detach
+
+# Error: front_matter_parser-0.2.1/lib/front_matter_parser/syntax_parser/multi_line_comment.rb:19:in `match': invalid byte sequence in US-ASCII (ArgumentError)
+# Workaround: https://stackoverflow.com/questions/17031651/invalid-byte-sequence-in-us-ascii-argument-error-when-i-run-rake-dbseed-in-ra
+export RUBYOPT="-KU -E utf-8:utf-8" # fixes front_matter_parser error within the `jekyll-sort reorder` call
+
+gem install jekyll-sort
+jekyll-sort reorder # Updates nav_order front matter of pages that are in the nav

data/.cody/docs/buildspec.yml

@@ -0,0 +1,10 @@
+version: 0.2
+
+phases:
+  build:
+    commands:
+      - .cody/docs/bin/build.sh
+cache:
+  paths:
+    - /usr/local/bundle
+    - /usr/local/lib/ruby/gems/2.5.0

data/.cody/docs/project.rb

@@ -0,0 +1,10 @@
+github_url("https://github.com/tongueroo/jets.git")
+linux_image("aws/codebuild/ruby:2.5.3-1.7.0")
+triggers(
+  webhook: true,
+  filter_groups: [[{type: "HEAD_REF", pattern: "master"}, {type: "EVENT", pattern: "PUSH"}]]
+)
+environment_variables(
+  SSH_KEY_S3_PATH: "ssm:/codebuild/jets/ssh_key_s3_path"
+)
+local_cache(true)

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,84 @@
+---
+name: Reproducible Bug Report
+about: Is something not working as expected?
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+<!--
+Hi! Thanks for considering to file a bug with Jets. Please take the time to
+answer the basic questions. Please try to be as detailed as possible.
+To be sensitive to everyone's time, if not enough details are provided, the
+issue may be closed without comment. If you repeatedly fail to provide enough
+details, you may be blocked from ever submitting issues to Jets again.
+Please use your best judgment. 👍
+
+If you are unsure this is a bug in Jets, please consider asking your question at:
+https://community.rubyonjets.com
+
+Thanks!
+-->
+
+## Checklist
+
+<!--
+Make sure that you've done all of these.  To mark a checkbox done, replace [ ] with [x]. Or after you create the issue you can click the checkbox.
+-->
+
+- [ ] Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a `jets upgrade` command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
+- [ ] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.rubyonjets.com
+- [ ] Code sample: Have you put together a code sample to reproduce the issue and make it available?  Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.
+
+## My Environment
+
+<!-- Please fill out the table below with debugging info to help: -->
+
+| Software         | Version |
+| ---------------- | ------- |
+| Operating System |         |
+| Jets             |         |
+| Ruby             |         |
+
+---
+
+## Expected Behaviour
+
+<!--
+What is it you expected to happen? This should be a description of how the functionality you tried to use is supposed to work. Try to keep this to one-paragraph.
+-->
+
+## Current Behavior
+
+<!--
+Describe the details of the bug.  Try to keep this to one-paragraph.
+-->
+
+## Step-by-step reproduction instructions
+
+<!--
+Be sure to include any steps you took for the problem to exist. This is likely the longest part of the report.
+
+Please include any logs you think relevant here. If the logs are long (more than 50 lines) please make a gist of the logs and link to it. https://gist.github.com
+
+With long logs, you can also use the <details> tag to keep the report readable. Example:
+
+<details>
+ <summary>Summary Goes Here</summary>
+
+ ...this is hidden, collapsable content. start with a blank line to get terminal output to format right...
+</details>
+-->
+
+## Code Sample
+
+<!--
+Please provide a code repository, gist, code snippet or sample files to reproduce the issue.
+-->
+
+## Solution Suggestion
+
+<!--
+Please provide possible solutions. If you can't think of anything, feel free to omit. Please be kind and add helpful possible solutions.  For example, "Fix it!" is not a helpful solution suggestion. We are mere mortals. Please be constructive.
+-->

data/.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,27 @@
+---
+name: Documentation
+about: Found a typo or something that isn't crystal clear in the docs?
+title: ''
+labels: docs
+assignees: ''
+
+---
+
+<!-- 
+Thanks for taking the time to open a documentation issue and help us make Jets better!
+
+Great documentation is key to great software and is very important. So thank you!
+
+If it is just a typo or grammar fix, you don't have to fill out any of the sections below. 🚀
+-->
+
+## Motivation
+
+<!-- Why should the docs be updated? -->
+
+
+## Suggestion
+
+<!-- What can be done instead? -->
+
+<!-- Thanks again for taking the time to open an issue and help us make Jets better! -->

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,64 @@
+---
+name: New Feature Suggestion
+about: Want to add a feature to Jets?
+title: ''
+labels: feature
+assignees: ''
+
+---
+
+<!--
+Hi! Thanks for considering to file a feature request with Jets. Please take the time to answer the basic questions. Please try to be as detailed as possible.
+
+Thanks!
+-->
+
+## Summary
+
+<!--
+A one-paragraph explanation of the feature.
+-->
+
+## Motivation
+
+<!--
+Why do you want to see this feature in Jets? What use cases does it support?
+
+How the feature would be relevant to 80% or more of Jets users.
+-->
+
+## Guide-level explanation
+
+<!--
+Explain the proposal as if it was already included in the project and you were teaching it to another programmer. That generally means:
+
+- Introducing new named concepts.
+- Explaining the feature largely in terms of examples.
+- If applicable, provide sample error messages, deprecation warnings, or upgrade guidance.
+
+If this is a small feature, you may omit this section.
+-->
+
+## Reference-level explanation
+
+<!--
+This is the technical portion of the feature request. Explain the design in sufficient detail that:
+
+- Its interaction with other features is clear.
+- It is reasonably clear how the feature would be implemented.
+- Corner cases are dissected by example.
+
+If you do not know how to answer this, you can omit it. No worries!
+-->
+
+## Drawbacks
+
+<!--
+Why should we *not* do this?
+-->
+
+## Unresolved Questions
+
+<!--
+What related issues do you consider out of scope for this feature that could be addressed in the future independently of the solution that comes out of this feature?
+-->

data/.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,14 @@
+---
+name: Question
+about: Have any questions about how Jets works?
+title: ''
+labels: 'question'
+assignees: ''
+
+---
+
+The Jets issue tracker IS NOT for usage questions! Please post your question on our dedicated forum at https://community.rubyonjets.com
+
+To be sensitive to everyone's time, we may close issues asking questions without comment. If you repeatedly post questions in the issues tracker, you may be blocked from ever submitting issues to Jets again. Please use your best judgment. 👍
+
+Posting your questions in the Jets community forum benefits others by grouping questions in a dedicated place. Here are some additional options also http://rubyonjets.com/docs/support/ 😁

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,7 @@
+Please fill out one of the templates on https://github.com/tongueroo/jets/issues/new/choose
+
+If you want to ask a question please do so on the Jets Community forum: https://community.rubyonjets.com
+
+To be sensitive to everyone's time, we may close issues asking questions without comment. Posting your questions in the Jets community forum is the best place. It also benefits others by making the questions easier to find. Here are some additional options also http://rubyonjets.com/docs/support/ 👌
+
+Thank you!

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,50 @@
+<!--
+Thanks for creating a Pull Request! Before you submit, please make sure you've done the following:
+
+- I read the contributing document at https://rubyonjets.com/docs/contributing/
+-->
+
+<!--
+Make our lives easier! Choose one of the following by uncommenting it:
+-->
+
+<!-- This is a 🐞 bug fix. -->
+<!-- This is a 🙋‍♂️ feature or enhancement. -->
+<!-- This is a 🧐 documentation change. -->
+
+<!--
+Before you submit this pull request, make sure to have a look at the following checklist. To mark a checkbox done, replace [ ] with [x]. Or after you create the issue you can click the checkbox.
+
+If you don't know how to do some of these, that's fine!  Submit your pull request and we will help you out on the way.
+-->
+
+- [ ] I've added tests (if it's a bug, feature or enhancement)
+- [ ] I've adjusted the documentation (if it's a feature or enhancement)
+- [ ] The test suite passes (run `bundle exec rspec` to verify this)
+
+## Summary
+
+<!--
+Provide a description of what your pull request changes.
+-->
+
+## Context
+
+<!--
+Is this related to any GitHub issue(s) or another relevant link?
+-->
+
+## How to Test
+
+<!--
+Please provide instructions on how to test the fix. This speeds up reviewing the PR. If testing requires a demo Jets project, please provide an example repo.
+-->
+
+
+## Version Changes
+
+<!--
+Which semantic version change would you recommend?
+If you don't know, feel free to omit it.
+-->
+

data/.gitignore

@@ -0,0 +1,24 @@
+*.gem
+*.rbc
+.bundle
+.byebug_history
+.config
+.yardoc
+_yardoc
+coverage
+doc/
+InstalledFiles
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+
+.codebuild/definitions
+/html
+/demo
+Gemfile.lock
+spec/fixtures/apps/franky/dynamodb/migrate
+spec/fixtures/project/handlers

data/.python-version

@@ -0,0 +1 @@
+3.8.6

data/.rspec

@@ -0,0 +1,4 @@
+--color
+--exclude-pattern spec/fixtures/apps/**/*
+--format documentation
+--require spec_helper

data/.ruby-gemset

@@ -0,0 +1 @@
+jets3017mount

data/.ruby-version

@@ -0,0 +1 @@
+2.7.2