verify-deutschified

The frontend for GOV.UK Verify, deutschified as a quick example prototype for a similar identity proofing solution in Germany. Repo is cloned from https://github.com/alphagov/verify-frontend. Instructions below are from the original repo.

Embarrassingly hacky, please ignore all the crossover variable names. The goal is just a clickable flow with the correct colors & logos & localization

Installing the application

Once you’ve cloned this then bundle will install the requirements.

Running the application

You can start the application without having any of the closed source components installed with:

./startup.sh --stub-api

This will start the frontend server running on http://localhost:50300/ and a stubbed API server on http://localhost:50199.

To start a journey on the front end visit http://localhost:50300/test-saml and click saml-post.

If you're on the Verify team and have the rest of the federation running locally you should omit the --stub-api argument and start your journey from the test-rp.

Running the tests

./pre-commit.sh

This will lint the application code and run the tests.

If you need to run the javascript-enabled tests that require a browser, you will need to have Chrome installed. The stable release of Chrome should work.

Editing .travis.yml

If you plan to edit this file please enable the pre-commit check which lints it, preventing mistakes. To do so, first install pre-commit and then run pre-commit install. On an OSX system this amounts to:

brew install pre-commit
pre-commit install

Deploying the application

The application is deployed using our CI/CD pipeline. Any changes merged to master are automatically deployed. This repo has an active branch protection for master. Any changes need to be raised via PR and approved by two other developers.

PR reviews

When a PR is raised, it's automatically tested using Travis (runs the ./pre-commit.sh script on the branch and against master) which is configured in the .travis file. The test results are shown directly on the PR.

In addition to the Travis tests we have also enabled Codacy to check coding style. Again, the results are shown within the PR. Codacy is configured using the .rubocop.yml file.

The PR is also deployed to Heroku as a review app. The app is destroyed when the PR is closed/merged or after 5 days of inactivity. It uses docker to run both the Rails app and the stub API server. The Heroku deployment is configured using the 4 files:

• Dockerfile.heroku - to configure the docker image of frontend
• heroku.yml - Heroku deployment manifest
• app.json - Heroku application manifest
• heroku-startup.sh - startup script used to start the app and api, on the port supplied by Heroku

Cross GOV.UK Domain Google Analytics

To track user journeys across the whole of GOV.UK, including Verify, Google Analytics code has been introduced to the Verify Frontend.

We will occasionally be asked to add domains to the list of domains for which cross domain tracking is enabled. This list is injected through the CROSS_GOV_GOOGLE_ANALYTICS_DOMAIN_LIST environment variable, which is set in the verify-infrastructure-config repository by setting the cross_gov_ga_domain_names variable in the site.tf for the relevant environment.