et_full_system 0.1.23

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: da3986668454b7fc15815045d987a9d673de349f70d36e54ff479c8045bfd180
+  data.tar.gz: 3ad3959a8f1a3e3d82677cad4a0a164e58eb6a6e29931e1f6e2fe33c3ab589a1
+SHA512:
+  metadata.gz: 0e8d1c984052513bb0f779a95f885cc1cc822fb338accc100fb4893ed5beb7287eed3584109e727b5dd2aa0bac0f9e30bffd7bcf420906c0e84919ed78241482
+  data.tar.gz: bdb4d8160d744f838af89ff06e8f75accac3a66195a39ca4ed40bb86ab61280dd8917617694f755ba7be2b8c00005b73211fc338fa6f8e88e00e6ca6c36a5c54

data/.gitignore

@@ -0,0 +1,12 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status
+/.idea

data/.rspec

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

data/.ruby-version

@@ -0,0 +1 @@
+2.5.1

data/.travis.yml

@@ -0,0 +1,7 @@
+deploy:
+  provider: rubygems
+  api_key:
+    secure: ayNLN94W/7OLlrbpOgszFYfx7cvhAYHLcW9NZG/gN4N0kUiwZ5f7vGGT2YDPSjiXdxLDnZfCdO5gmMjP59XyWqq4n3HxG5PipsZ5HjOp+nuUh/PzPB7YXizFCjGm9ggIUrBcE3pdrD7hYuKmMlnDjnAcgOQn+zw+QHNGmV3mJhSNuo+Vp/GotU8aAITHCQZUsSMQZQMGjoGG5yf+BAhJSf+mpPBNIoqdI/di8W2rzynwQJeN19/O7M1evAyt/vFVgNlwBE2YaEc7RWn3fhWV6O7nJSFTbGEv5gsMZYPRRWrw2DvBfnhCD4T3jC/hfuMybOUNbF9waktaxKeWVvKiYqQsDPYoh/3H/PViU/sFwKbU2jsxqAUkIBA5yhQXYk4FcKBUInHAIQE3dGy0eBa+hGC0u6sC9mwy3OFWiAfIPU8Fq+dW6e8N7ebJ1NW2UOxJLZjO2AS4LB2A2pMn/wTwm+ru3gVWqM3CF6vr4nc/hpj7DIFuI0OVDLNLeBzfV0Q8frxW8HoYgO2S/7RKXlT5PvwE+6pES2EEADa6LblZCVv6pu0VzVmuUNJ51HkUNYuCHIubXpyJBJGaFpG35q+u05Dh6MPVb+ZtSdNlG9Mw4Rcwpn6rE77+Mkh0TQ1q39SSO1odI6wONi6KTatuK56tV4tTL1fQBgtzYA4Gfl6z+OA=
+  on:
+    tags: true
+  gem: et_full_system

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at gary.taylor@hismessages.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,7 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in et_full_system.gemspec
+gem 'et_fake_acas_server', git: 'https://github.com/ministryofjustice/et_fake_acas_server.git', ref: 'bca2a727c0bd8a16915eee499d0bb3e97ddc5cf0'
+gemspec

data/Gemfile.lock

@@ -0,0 +1,115 @@
+GIT
+  remote: https://github.com/ministryofjustice/et_fake_acas_server.git
+  revision: bca2a727c0bd8a16915eee499d0bb3e97ddc5cf0
+  ref: bca2a727c0bd8a16915eee499d0bb3e97ddc5cf0
+  specs:
+    et_fake_acas_server (0.1.0)
+      activesupport (~> 5.2)
+      nokogiri (~> 1.8, >= 1.8.2)
+      puma (~> 3.12)
+      ruby-mcrypt (~> 0.2)
+      sinatra (~> 2.0, >= 2.0.3)
+      sinatra-contrib (~> 2.0)
+
+PATH
+  remote: .
+  specs:
+    et_full_system (0.1.23)
+      aws-sdk-s3 (~> 1.9)
+      azure-storage (~> 0.15.0.preview)
+      dotenv (~> 2.7, >= 2.7.2)
+      httparty (~> 0.16)
+      thor (~> 0.20)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (5.2.3)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 0.7, < 2)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    aws-eventstream (1.0.3)
+    aws-partitions (1.154.0)
+    aws-sdk-core (3.48.6)
+      aws-eventstream (~> 1.0, >= 1.0.2)
+      aws-partitions (~> 1.0)
+      aws-sigv4 (~> 1.1)
+      jmespath (~> 1.0)
+    aws-sdk-kms (1.17.0)
+      aws-sdk-core (~> 3, >= 3.48.2)
+      aws-sigv4 (~> 1.1)
+    aws-sdk-s3 (1.36.1)
+      aws-sdk-core (~> 3, >= 3.48.2)
+      aws-sdk-kms (~> 1)
+      aws-sigv4 (~> 1.0)
+    aws-sigv4 (1.1.0)
+      aws-eventstream (~> 1.0, >= 1.0.2)
+    azure-core (0.1.15)
+      faraday (~> 0.9)
+      faraday_middleware (~> 0.10)
+      nokogiri (~> 1.6)
+    azure-storage (0.15.0.preview)
+      azure-core (~> 0.1)
+      faraday (~> 0.9)
+      faraday_middleware (~> 0.10)
+      nokogiri (~> 1.6, >= 1.6.8)
+    backports (3.13.0)
+    concurrent-ruby (1.1.5)
+    dotenv (2.7.2)
+    faraday (0.15.4)
+      multipart-post (>= 1.2, < 3)
+    faraday_middleware (0.13.1)
+      faraday (>= 0.7.4, < 1.0)
+    httparty (0.17.0)
+      mime-types (~> 3.0)
+      multi_xml (>= 0.5.2)
+    i18n (1.6.0)
+      concurrent-ruby (~> 1.0)
+    jmespath (1.4.0)
+    mime-types (3.2.2)
+      mime-types-data (~> 3.2015)
+    mime-types-data (3.2019.0331)
+    mini_portile2 (2.4.0)
+    minitest (5.11.3)
+    multi_json (1.13.1)
+    multi_xml (0.6.0)
+    multipart-post (2.0.0)
+    mustermann (1.0.3)
+    nokogiri (1.10.2)
+      mini_portile2 (~> 2.4.0)
+    puma (3.12.1)
+    rack (2.0.7)
+    rack-protection (2.0.5)
+      rack
+    rake (10.5.0)
+    ruby-mcrypt (0.2.0)
+    sinatra (2.0.5)
+      mustermann (~> 1.0)
+      rack (~> 2.0)
+      rack-protection (= 2.0.5)
+      tilt (~> 2.0)
+    sinatra-contrib (2.0.5)
+      backports (>= 2.8.2)
+      multi_json
+      mustermann (~> 1.0)
+      rack-protection (= 2.0.5)
+      sinatra (= 2.0.5)
+      tilt (>= 1.3, < 3)
+    thor (0.20.3)
+    thread_safe (0.3.6)
+    tilt (2.0.9)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  et_fake_acas_server!
+  et_full_system!
+  rake (~> 10.0)
+
+BUNDLED WITH
+   1.17.3

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Gary Taylor
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,194 @@
+# EtFullSystem
+
+This gem is used to boot up all of the components of the Employment Tribunals system ready for testing or other purposes.
+
+It can be used in the root directory of the 'et full system' repository (https://github.com/ministryofjustice/et-full-system) to run
+the server side to allow automated testing.
+
+But, in general - it can be used anywhere - as long as a certain file structure exists for the 5 services.  This structure is
+
+systems/et1 (https://github.com/ministryofjustice/atet)
+systems/et3 (https://github.com/ministryofjustice/et3)
+systems/admin (https://github.com/ministryofjustice/et-admin)
+systems/atos (https://github.com/ministryofjustice/et_atos_file_transfer)
+systems/api (https://github.com/ministryofjustice/et_api)
+
+The system works by placing a reverse proxy (traefik https://github.com/containous/traefik) in front of the 5 services
+so that all services can be accessed using a standard subdomain based url system which looks like this
+
+et1.et.127.0.0.1.nip.io:3100 For ET1
+et3.et.127.0.0.1.nip.io:3100 For ET3
+admin.et.127.0.0.1.nip.io:3100 For Admin
+et1.et.127.0.0.1.nip.io:3100 For ET1
+et1.et.127.0.0.1.nip.io:3100 For ET1
+
+The services are run all together using 'forego' (like foreman - runs a Procfile) and once the port number for each
+service is known, traefik is told about it - so it all just works.
+
+There are other services as well that are run - which are there for testing - these are :-
+
+* et-fake-acas-server (https://github.com/ministryofjustice/et_fake_acas_server) - Provides a fake ACAS server with predictable responses based on various special certificate numbers
+* mailhog (https://github.com/mailhog/MailHog) - Captures all emails sent to allow the test suite or the developer to view them and check them
+* minio (https://github.com/minio/minio) - A local amazon S3 server to avoid having S3 credentials for every environment
+* azurite (https://github.com/Azure/Azurite) - A local azure blob server to avoid having azure credentials for every environment
+
+
+## Pre Requisites
+
+### Running With Docker
+
+If you want to use the docker setup, it keeps everything inside a container and therefore doesnt interfere with your
+system configuration at all.  All you need is
+
+* Docker
+* Docker Compose
+
+### Running Without Docker
+
+To run without docker, you need a few tools
+
+* Traefik (https://traefik.io)
+* Mailhog (https://github.com/mailhog/MailHog)
+* Minio (https://github.com/minio/minio)
+* Azurite (https://github.com/Azure/Azurite)
+
+I will not include installation instructions here for them - please visit their web sites and install them on your platform.
+For OSX users check out the homebrew repository - there are formulas for some of these.
+
+## Installation
+
+At the moment, this gem is not published anywhere - it is too specific to be published to rubygems.
+
+So, there are 2 ways of installing it - using bundler from an existing project (et_full_system uses it) and installing from
+github directly.
+
+### Using Bundler
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'et_full_system', '0.1.17', git: 'https://github.com/hmcts/et_full_system_gem.git', ref: '2b684106ae42affaffe454ac190f65d55d9baab9'
+```
+
+Replacing the version numbers and git ref according to the latest version.
+
+And then execute:
+
+    $ bundle
+
+And if you want to install a binstub (do bundle help binstubs for more options you might want)
+
+    $ bundle binstubs et_full_system --standalone
+
+### Installing Direct From Github
+
+Or install it yourself directly from github as follows:
+
+    $ git checkout git@github.com:hmcts/et_full_system_gem.git
+    $ cd et_full_system_gem
+    $ gem build et_full_system -o et_full_system.gem
+    $ gem install et_full_system.gem
+    $ rm et_full_system.gem
+
+## Usage (using docker)
+
+To setup the docker system
+
+    $ et_full_system docker setup
+
+To start the server (Must have been setup with the command above - for the first time and after changing gems etc.. in the services)
+
+    $ et_full_system docker server
+
+To reset the server (Note: no other docker containers should be sharing the network - such as a test container)
+
+    $ et_full_system docker reset
+
+To setup and start the server in detached mode (i.e showing no logs etc..)
+
+    $ et_full_system docker server -d
+
+To watch the logs of an existing running server
+
+    $ et_full_system docker compose logs -f
+
+To do any other docker compose commands
+
+    $ et_full_system docker compose <command> <command args>
+
+To redirect a service to your own hosted version
+
+If you want to host a service yourself for debugging or other purposes - you must setup the service yourself with all
+the relevant environment variables (see the service_env command), then, to point the full system url's to your hosted service, use the following command
+
+    $ et_full_system docker update_service_url <service_name> <service_url>
+
+Where <service_name> is either et1, et3, admin, api or atos
+and <service_url> must be a URL that is reachable from the docker container - you may need to use the special 'host.docker.internal'
+or in general checkout this page https://docs.docker.com/docker-for-mac/networking/ or https://docs.docker.com/docker-for-windows/networking/
+
+
+## Usage (Without docker)
+
+To setup the local system
+
+    $ et_full_system local setup
+
+To start the server (Must have been setup with the command above - for the first time and after changing gems etc.. in the services)
+
+    $ et_full_system local server
+
+To reset the server - this will drop and recreate the database, empty redis etc..  so VERY destructive
+
+    $ et_full_system local reset
+
+To redirect a service to your own hosted version
+
+If you want to host a service yourself for debugging or other purposes - you must setup the service yourself with all
+the relevant environment variables (see the service_env command), then, to point the full system url's to your hosted service, use the following command
+
+    $ et_full_system local update_service_url <service_name> <service_url>
+
+Where <service_name> is either et1, et3, admin, api or atos
+
+To setup the environment variables in the current shell to allow you to run a service manually for debugging for example
+
+    $ export $(et_full_system local service_env <service_name>)
+
+
+    Where <service_name> is either et1, et3, admin, api or atos
+
+If for any reason, there are services that you don't want - you might just want to save resources and are not interested in
+every part of the system, you can use the --without option on the server command as follows
+
+    $ et_full_system local server --without=et3_web fake_acas_web
+
+To see all options - do
+
+    $ et_full_system local server --help
+
+### Upgrading
+
+Note that docker caches stuff for the better and for the worse.  So, the command in the Dockerfile that installs the version
+of the gem that you have - but inside docker - will be cached forever - only if the command changes in the Dockerfile is this
+cache busted.
+
+So, for now - until there is a more automated solution to this, whenever a new version of this gem is installed - simply reset using the following command
+
+    $ et_full_system docker reset
+
+Which will re build it from scratch - then just use the gem as normal (it will have been setup by this command so you can
+go straight to using the server command)
+
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/hmcts/et_full_system_gem. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the EtFullSystem project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/hmcts/et_full_system_gem/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+
+desc "Default task - does nothing apart from keep travis happy"
+task :default do
+
+end

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "et_full_system"
+
+# 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/docker/Dockerfile

@@ -0,0 +1,103 @@
+FROM phusion/passenger-customizable:0.9.34
+# Set correct environment variables.
+ENV HOME /root
+
+# Use baseimage-docker's init process.
+CMD ["/sbin/my_init"]
+
+# If you're using the 'customizable' variant, you need to explicitly opt-in
+# for features.
+#
+# N.B. these images are based on https://github.com/phusion/baseimage-docker,
+# so anything it provides is also automatically on board in the images below
+# (e.g. older versions of Ruby, Node, Python).
+#
+# Uncomment the features you want:
+#
+#   Ruby support
+
+# The following 2 lines are temporary - see https://github.com/phusion/passenger-docker/issues/234
+# Try to remove and build from scratch maybe after january 2019
+RUN curl -sSL https://rvm.io/pkuczynski.asc | gpg --import -
+RUN curl -sSL https://rvm.io/mpapis.asc -o /pd_build/ruby_support/mpapis-pubkey.asc
+#RUN /pd_build/ruby-2.0.*.sh
+#RUN /pd_build/ruby-2.1.*.sh
+#RUN /pd_build/ruby-2.2.*.sh
+#RUN /pd_build/ruby-2.3.*.sh
+#RUN /pd_build/ruby-2.4.*.sh
+RUN /pd_build/ruby-2.5.*.sh
+#RUN /pd_build/jruby-9.1.*.sh
+#   Python support.
+#RUN /pd_build/python.sh
+#   Node.js and Meteor standalone support.
+#   (not needed if you already have the above Ruby support)
+#RUN /pd_build/nodejs.sh
+
+# Get latest rubygems
+RUN bash --login -c "rvm --default use 2.5.1"
+RUN gem update --system
+
+# ...put your own build instructions here...
+RUN apt-get update && apt-get -y install pdftk tzdata postgresql gettext-base wget sudo libmcrypt-dev mcrypt
+
+RUN /pd_build/nodejs.sh
+
+# Enable the Redis service.
+RUN rm -f /etc/service/redis/down
+
+# Install forego (for Procfile running)
+RUN bash -lc "wget https://bin.equinox.io/c/ekMN3bCZFUn/forego-stable-linux-amd64.deb && apt install ./forego-stable-linux-amd64.deb && rm ./forego-stable-linux-amd64.deb"
+
+# Install traefik (For front end reverse proxy)
+RUN bash -lc "wget https://github.com/containous/traefik/releases/download/v1.7.10/traefik_linux-amd64 && mv ./traefik_linux-amd64 /usr/bin/traefik && chmod +x /usr/bin/traefik"
+
+# Install minio
+RUN bash -lc "cd /usr/local/bin && wget https://dl.minio.io/server/minio/release/linux-amd64/minio && chmod +x minio"
+
+# Install azurite
+RUN bash -lc "npm install -g azurite"
+
+# Install Mailhog
+RUN bash -lc "cd /usr/local/bin && wget https://github.com/mailhog/MailHog/releases/download/v1.0.0/MailHog_linux_amd64 -O mailhog && chmod +x mailhog"
+
+# Create the minio_data directory for the minio server
+RUN mkdir -p /home/app/minio_data; chown app:app /home/app/minio_data; chmod 0777 /home/app/minio_data
+
+# Create the azure_storage_data directory for the azure storage server
+RUN mkdir -p /home/app/azure_storage_data; chown app:app /home/app/azure_storage_data; chmod 0777 /home/app/azure_storage_data
+
+# Clean up APT when done.
+RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
+
+RUN mkdir -p /home/app/full_system; chown app:app /home/app/full_system
+# Install gems and binstubs to run without bundler
+RUN mkdir -p /home/app/system_gems/et_full_system && chmod 0777 /home/app/system_gems/et_full_system && chown -R app:app /home/app/system_gems
+
+RUN usermod -o -u 1000 app
+RUN groupmod -o -g 1000 app
+WORKDIR /home/app/full_system
+RUN echo "app ALL=(root) NOPASSWD:ALL" > /etc/sudoers.d/user && chmod 0440 /etc/sudoers.d/user
+USER app
+
+
+
+RUN bash --login -c "rvm --default use 2.5.1"
+RUN bash --login -c "gem install bundler"
+
+# Bundle install the gem itself to fetch all its dependencies defined in the Gemfile (git deps - hence the complex stuff) - then build and install the full system gem and fake acas server so they are available
+# as commands not needing bundle exec etc...
+COPY . /home/app/system_gems/et_full_system
+WORKDIR /home/app/system_gems/et_full_system
+RUN sudo chown -R app:app .
+RUN bash --login -c "ls -al /home/app/system_gems/et_full_system"
+RUN bash --login -c "rvm use && bundle install"
+RUN bash --login -c "rvm use && gem install dotenv"
+
+RUN bash --login -c "rvm use && gem build et_full_system -o /tmp/et_full_system.gem && gem install /tmp/et_full_system.gem && rm /tmp/et_full_system.gem"
+RUN bash --login -c "rvm use && cd /usr/local/rvm/gems/ruby-2.5.1/bundler/gems/et_fake_acas_server* && gem build et_fake_acas_server -o /tmp/et_fake_acas_server.gem && gem install /tmp/et_fake_acas_server.gem && rm //tmp/et_fake_acas_server.gem"
+
+WORKDIR /home/app/full_system
+
+
+RUN cd /home/app
+ENV HOME /home/app