rails_template_18f 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: daa50caac6d934e7a1d6611ac427068601ad836f81fab7b088aed2b47de3724b
+  data.tar.gz: 7dd5b479db57b51ce6eadbe53134605a346db5de2e4c490510a59c3ec56f644b
+SHA512:
+  metadata.gz: '08bba6304087afcfda8ac54101628312329963338a36ed488768bdfdc2a296a9b54140df951108eaa8cbc563d29cd35a461379e6039d17a4f910a50b60313890'
+  data.tar.gz: ad54e4be93ee88883503ed96f6a7ace02f00509d584b02e122b7fb66117a2baf6cd19f444f3f74f26c3209280be0204926e3ab2e8c217a1a59d600572b7f9abe

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.standard.yml

@@ -0,0 +1,2 @@
+# For available configuration options, see:
+#   https://github.com/testdouble/standard

data/CHANGELOG.md

@@ -0,0 +1,6 @@
+## [Unreleased]
+
+## [0.1.0] - 2022-02-14
+
+- Initial release
+- circleci and github_actions generators for adding CI/CD pipeline to your project

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at ryan.ahearn@gsa.gov. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in rails-template-18f.gemspec
+gemspec
+
+gem "rake", "~> 13.0"
+
+gem "colorize", "~> 0.8"

data/Gemfile.lock

@@ -0,0 +1,132 @@
+PATH
+  remote: .
+  specs:
+    rails_template_18f (0.1.0)
+      activesupport (~> 7.0.0)
+      railties (~> 7.0.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actionpack (7.0.2.2)
+      actionview (= 7.0.2.2)
+      activesupport (= 7.0.2.2)
+      rack (~> 2.0, >= 2.2.0)
+      rack-test (>= 0.6.3)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.2.0)
+    actionview (7.0.2.2)
+      activesupport (= 7.0.2.2)
+      builder (~> 3.1)
+      erubi (~> 1.4)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.1, >= 1.2.0)
+    activesupport (7.0.2.2)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      tzinfo (~> 2.0)
+    ammeter (1.1.5)
+      activesupport (>= 3.0)
+      railties (>= 3.0)
+      rspec-rails (>= 2.2)
+    ast (2.4.2)
+    builder (3.2.4)
+    colorize (0.8.1)
+    concurrent-ruby (1.1.9)
+    crass (1.0.6)
+    diff-lcs (1.5.0)
+    erubi (1.10.0)
+    i18n (1.9.1)
+      concurrent-ruby (~> 1.0)
+    loofah (2.14.0)
+      crass (~> 1.0.2)
+      nokogiri (>= 1.5.9)
+    method_source (1.0.0)
+    minitest (5.15.0)
+    nokogiri (1.13.1-x86_64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.13.1-x86_64-linux)
+      racc (~> 1.4)
+    parallel (1.21.0)
+    parser (3.1.0.0)
+      ast (~> 2.4.1)
+    racc (1.6.0)
+    rack (2.2.3)
+    rack-test (1.1.0)
+      rack (>= 1.0, < 3)
+    rails-dom-testing (2.0.3)
+      activesupport (>= 4.2.0)
+      nokogiri (>= 1.6)
+    rails-html-sanitizer (1.4.2)
+      loofah (~> 2.3)
+    railties (7.0.2.2)
+      actionpack (= 7.0.2.2)
+      activesupport (= 7.0.2.2)
+      method_source
+      rake (>= 12.2)
+      thor (~> 1.0)
+      zeitwerk (~> 2.5)
+    rainbow (3.1.1)
+    rake (13.0.6)
+    regexp_parser (2.2.0)
+    rexml (3.2.5)
+    rspec (3.11.0)
+      rspec-core (~> 3.11.0)
+      rspec-expectations (~> 3.11.0)
+      rspec-mocks (~> 3.11.0)
+    rspec-core (3.11.0)
+      rspec-support (~> 3.11.0)
+    rspec-expectations (3.11.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-mocks (3.11.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-rails (5.1.0)
+      actionpack (>= 5.2)
+      activesupport (>= 5.2)
+      railties (>= 5.2)
+      rspec-core (~> 3.10)
+      rspec-expectations (~> 3.10)
+      rspec-mocks (~> 3.10)
+      rspec-support (~> 3.10)
+    rspec-support (3.11.0)
+    rubocop (1.25.1)
+      parallel (~> 1.10)
+      parser (>= 3.1.0.0)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml
+      rubocop-ast (>= 1.15.1, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 3.0)
+    rubocop-ast (1.15.1)
+      parser (>= 3.0.1.1)
+    rubocop-performance (1.13.2)
+      rubocop (>= 1.7.0, < 2.0)
+      rubocop-ast (>= 0.4.0)
+    ruby-progressbar (1.11.0)
+    standard (1.7.1)
+      rubocop (= 1.25.1)
+      rubocop-performance (= 1.13.2)
+    thor (1.2.1)
+    tzinfo (2.0.4)
+      concurrent-ruby (~> 1.0)
+    unicode-display_width (2.1.0)
+    zeitwerk (2.5.4)
+
+PLATFORMS
+  x86_64-darwin-20
+  x86_64-linux
+
+DEPENDENCIES
+  ammeter (~> 1.1)
+  colorize (~> 0.8)
+  rails_template_18f!
+  rake (~> 13.0)
+  rspec (~> 3.11)
+  standard (~> 1.3)
+
+BUNDLED WITH
+   2.2.32

data/LICENSE.md

@@ -0,0 +1,21 @@
+# License
+
+As a work of the [United States government](https://www.usa.gov/), this project is in the public domain within the United States of America.
+
+Additionally, we waive copyright and related rights in the work worldwide through the CC0 1.0 Universal public domain dedication.
+
+## CC0 1.0 Universal Summary
+
+This is a human-readable summary of the [Legal Code (read the full text)](https://creativecommons.org/publicdomain/zero/1.0/legalcode).
+
+### No Copyright
+
+The person who associated a work with this deed has dedicated the work to the public domain by waiving all of their rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law.
+
+You can copy, modify, distribute, and perform the work, even for commercial purposes, all without asking permission.
+
+### Other Information
+
+In no way are the patent or trademark rights of any person affected by CC0, nor are the rights that other persons may have in the work or in how the work is used, such as publicity or privacy rights.
+
+Unless expressly stated otherwise, the person who associated a work with this deed makes no warranties about the work, and disclaims liability for all uses of the work, to the fullest extent permitted by applicable law. When using or citing the work, you should not imply endorsement by the author or the affirmer.

data/README.md

@@ -0,0 +1,140 @@
+18F-Flavored Rails 7 Project
+============================
+
+This template will create a new Rails 7.0.x project.
+
+See the `rails-6` branch for Rails 6.1.x
+
+## Use for new Rails Project
+
+1. Clone this repository to your computer
+1. Change directory into the clone
+1. Run `rails new <<PATH_TO_PROJECT>> --rc=<<RC_FILE>>` with the appropriate rc file for your needs. The path should not be a subdirectory of this repository.
+
+### Choosing which RC file to use
+
+You should run this template with either `railsrc` or `railsrc-hotwire` depending on your development needs.
+
+#### Server Rendered _or_ Single Page Applications
+
+`rails new <<PATH_TO_PROJECT>> --rc=railsrc`
+
+The base `railsrc` file creates a Rails application that is appropriate for both server-rendered applications,
+as well as a basis for installing a separate Single Page Application (SPA) library such as React.
+
+#### A bit more JavaScript needed
+
+`rails new <<PATH_TO_PROJECT>> --rc=railsrc-hotwire`
+
+The `railsrc-hotwire` file creates a Rails application that includes the [Hotwire](https://hotwired.dev/) JavaScript framework.
+
+Hotwire can be used to add [a bit of JavaScript](https://engineering.18f.gov/web-architecture/#:~:text=are%20more%20complex-,If%20your%20use%20case%20requires%20a%20bit%20of%20client%2Dside%20interactivity%2C%20use%20the%20above%20options%20with%20a%20bit%20of%20JavaScript.,-You%20might%20use)
+for more interactivity than server-rendered apps, but less than a full SPA.
+
+### Available Options
+
+The following options can be added after `--rc=<<RC_FILE>>` to change how the template behaves.
+
+**Important:** You must not pass `--skip-bundle` or `--skip-javascript` to `rails new` or various aspects of the template will be broken
+
+#### `--javascript=esbuild`
+
+Use [esbuild](https://esbuild.github.io/) instead of [webpack](https://webpack.js.org/) for JavaScript bundling. Note that
+maintaining IE11 support with esbuild may be tricky.
+
+#### `--no-skip-FRAMEWORK`
+
+Each of the skipped frameworks in `railsrc` can be overridden on the command line. For example: `--no-skip-active-storage` will include support for `ActiveStorage` document uploads
+
+### What `railsrc` does
+
+```
+--skip-active-storage   # don't include ActiveStorage for document upload
+--skip-action-text      # don't include ActionText libraries for WYSIWYG editing
+--skip-action-cable     # don't include ActionCable websocket implementation
+--skip-action-mailbox   # don't include inbound email
+--skip-hotwire          # don't include Hotwire JS library
+--skip-test             # Skip built in test framework. (RSpec included via template.rb)
+--javascript=webpack    # Use webpack for JS bundling
+--css=postcss           # Use the postcss CSS bundling framework
+--template=template.rb  # add additional configuration from template.rb
+--database=postgresql   # default to PostgreSQL
+```
+
+### What `railsrc-hotwire` does
+
+`railsrc-hotwire` is identical to `railsrc` except that [Hotwire](https://hotwired.dev/) and [ActionCable](https://guides.rubyonrails.org/action_cable_overview.html) are not skipped.
+
+ActionCable is included to enable the [Turbo Streams](https://turbo.hotwired.dev/handbook/streams) functionality of Hotwire.
+
+
+### What `template.rb` does
+
+1. Create a better default `README`
+1. Copy `CONTRIBUTING.md` and `LICENSE.md` from the [18F Open Source Policy repo](https://github.com/18F/open-source-policy/)
+1. Create a "near-production" `ci` Rails environment, used for running a11y and security scans
+1. Create a "near-production" `staging` Rails environment, used for cloud.gov staging environment, with a "TEST SITE" warning banner
+1. Create a `.nvmrc` file for specifying the NodeJS version in use
+1. Set up `pa11y-ci` for a11y scanning
+1. Set up `OWASP ZAP` dynamic security scanning
+1. Include `secure_headers` gem and configure CSP header to get OWASP passing by default
+1. Install and configure [brakeman](https://rubygems.org/gems/brakeman) for static security scanning
+1. Install `bundler-audit` and set up `bundle:audit` rake task for Ruby dependency security scans
+1. Set up `yarn:audit` rake task for JavaScript dependency security scans
+1. Install [Standard Ruby](https://github.com/testdouble/standard) for Ruby linting
+1. Install [rspec](https://rubygems.org/gems/rspec-rails) for unit testing
+1. Install [dotenv](https://rubygems.org/gems/dotenv-rails) for local configuration
+1. Setup Rails credential diffing
+1. Create a separate production credentials file.
+1. Create a `pre-commit` hook that can be used to automatically run ruby linter & terraform format
+1. Setup USWDS via postcss
+1. Setup webpack with `.browserslistrc` from USWDS
+1. Update `app/views/layouts/application.html.erb` to pass the `pa11y-ci` scan and include the USWDS Banner
+1. Create a `PagesController` and root route
+1. Create boundary and logical data model compliance diagrams
+1. Create `manifest.yml` and variable files for cloud.gov deployment
+1. Optionally run the `rake db:create` and `rake db:migrate` setup steps
+1. Optionally create Github Actions workflows for testing and cloud.gov deploy
+1. Optionally create terraform modules supporting staging & production cloud.gov spaces
+1. Optionally create CircleCI workflows for testing and cloud.gov deploy
+1. Optionally create [Architecture Decision Records](https://adr.github.io/) for above setup
+1. Optionally create a New Relic config with FEDRAMP-specific host
+1. Optionally configure DAP (Digital Analytics Program)
+1. Optionally add base translation files and routes for Spanish, French, and Simplified Chinese (es.yml, fr.yml, and zh.yml)
+1. Commit the resulting project with git (unless `--skip-git` is passed)
+
+## Use for an existing Rails project
+
+### Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem "rails-template-18f"
+```
+
+And then run:
+
+  $ bundle install
+
+Or install it yourself as:
+
+  $ gem install rails-template-18f
+
+### Usage
+
+Run `rails generate` for a list of commands this gem can run
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/rahearn/rails-template-18f. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/rahearn/rails-template-18f/blob/main/CODE_OF_CONDUCT.md).
+
+## Code of Conduct
+
+Everyone interacting in the 18F Rails Template project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/rahearn/rails-template-18f/blob/main/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "standard/rake"
+
+task default: %i[spec standard]

data/bin/console

@@ -0,0 +1,16 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require "rails/all"
+require "rails_template_18f"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/generators/rails_template18f/circleci/circleci_generator.rb

@@ -0,0 +1,116 @@
+# frozen_string_literal: true
+
+module RailsTemplate18f
+  module Generators
+    class CircleciGenerator < ::Rails::Generators::Base
+      include ::Rails::Generators::AppName
+      include RailsTemplate18f::TerraformOptions
+
+      desc <<~DESC
+        Description:
+          Install CircleCI pipeline files
+      DESC
+
+      def self.source_root
+        @source_root ||= File.expand_path(File.join(File.dirname(__FILE__), "templates"))
+      end
+
+      def install_needed_gems
+        gem "rspec_junit_formatter", "~> 0.5", group: :test
+      end
+
+      def install_pipeline
+        directory "circleci", ".circleci"
+        copy_file "docker-compose.ci.yml"
+        template "Dockerfile"
+        copy_file "bin/ci-server-start", mode: :preserve
+      end
+
+      def update_readme
+        insert_into_file "README.md", readme_cicd, after: "## CI/CD\n"
+        insert_into_file "README.md", readme_staging_deploy, after: "#### Staging\n"
+        insert_into_file "README.md", readme_prod_deploy, after: "#### Production\n"
+        insert_into_file "README.md", readme_credentials, after: "#### Credentials and other Secrets\n"
+      end
+
+      def update_boundary_diagram
+        boundary_filename = "doc/compliance/apps/application.boundary.md"
+        insert_into_file boundary_filename, <<EOB, after: "Boundary(cicd, \"CI/CD Pipeline\") {\n"
+    System_Ext(github, "GitHub", "GSA-controlled code repository")
+    System_Ext(circleci, "CircleCI", "Continuous Integration Service")
+EOB
+        insert_into_file boundary_filename, <<~EOB, before: "@enduml"
+          Rel(developer, github, "Publish code", "git ssh (22)")
+          Rel(github, circleci, "Commit hook notifies CircleCI to run CI/CD pipeline", "https POST (443)")
+          Rel(circleci, cg_api, "Deploy App", "Auth: SpaceDeployer Service Account, https (443)")
+        EOB
+      end
+
+      no_tasks do
+        def readme_cicd
+          <<~EOM
+
+            CircleCI is used to run all tests and scans as part of pull requests.
+
+            Security scans are also run on a daily schedule.
+          EOM
+        end
+
+        def readme_staging_deploy
+          <<~EOM
+
+            Deploys to staging#{terraform? ? ", including applying changes in terraform," : ""} happen
+            on every push to the `main` branch in Github.
+
+            The following secrets must be set within [CircleCI Environment Variables](https://circleci.com/docs/2.0/env-vars/)
+            to enable a deploy to work:
+
+            | Secret Name | Description |
+            | ----------- | ----------- |
+            | `CF_STAGING_USERNAME` | cloud.gov SpaceDeployer username |
+            | `CF_STAGING_PASSWORD` | cloud.gov SpaceDeployer password |
+            | `RAILS_MASTER_KEY` | `config/master.key` |
+            #{terraform_secret_values}
+          EOM
+        end
+
+        def readme_prod_deploy
+          <<~EOM
+
+            Deploys to production#{terraform? ? ", including applying changes in terraform," : ""} happen
+            on every push to the `production` branch in Github.
+
+            The following secrets must be set within [CircleCI Environment Variables](https://circleci.com/docs/2.0/env-vars/)
+            to enable a deploy to work:
+
+            | Secret Name | Description |
+            | ----------- | ----------- |
+            | `CF_PRODUCTION_USERNAME` | cloud.gov SpaceDeployer username |
+            | `CF_PRODUCTION_PASSWORD` | cloud.gov SpaceDeployer password |
+            | `PRODUCTION_RAILS_MASTER_KEY` | `config/credentials/production.key` |
+            #{terraform_secret_values}
+          EOM
+        end
+
+        def readme_credentials
+          <<~EOM
+
+            1. Store variables that must be secret using [CircleCI Environment Variables](https://circleci.com/docs/2.0/env-vars/)
+            1. Add the appropriate `--var` addition to the `cf push` line on the deploy job
+          EOM
+        end
+      end
+
+      private
+
+      def terraform_secret_values
+        if terraform?
+          <<~EOM
+            | `AWS_ACCESS_KEY_ID` | Access key for terraform state bucket |
+            | `AWS_SECRET_ACCESS_KEY` | Secret key for terraform state bucket |
+          EOM
+        end
+      end
+    end
+  end
+end

data/lib/generators/rails_template18f/circleci/templates/Dockerfile.tt

@@ -0,0 +1,13 @@
+FROM cimg/ruby:<%= ruby_version %>-node
+
+ENV PORT=3000
+EXPOSE $PORT
+
+COPY --chown=circleci . /home/circleci/project
+RUN bundle install --deployment
+RUN yarn install --frozen-lockfile
+
+ENV RAILS_ENV=ci
+RUN bundle exec rake assets:precompile
+
+CMD ["./bin/ci-server-start"]

data/lib/generators/rails_template18f/circleci/templates/bin/ci-server-start

@@ -0,0 +1,8 @@
+#!/bin/bash
+#
+# this script is used by docker-compose and Dockerfile to start up a servrer
+# for running OWASP in CircleCI
+
+dockerize -wait tcp://db:5432 -timeout 1m
+bundle exec rails db:schema:load --trace
+bundle exec rails server -b 0.0.0.0