fg-cw-frontend

Case worker frontend application

• Requirements
  • Node.js
• Server-side Caching
• Redis
• Local Development
  • Setup
  • Development
  • Production
  • Npm scripts
  • Update dependencies
  • Formatting
    • Windows prettier issue
• Docker
  • Development image
  • Production image
  • Docker Compose
  • Dependabot
  • SonarCloud
• Licence
  • About the licence

Requirements

Node.js

Please install Node.js >= v18 and npm >= v9. You will find it easier to use the Node Version Manager nvm

To use the correct version of Node.js for this application, via nvm:

cd fg-cw-frontend
nvm use

Server-side Caching

We use Catbox for server-side caching. By default the service will use CatboxRedis when deployed and CatboxMemory for local development. You can override the default behaviour by setting the SESSION_CACHE_ENGINE environment variable to either redis or memory.

Please note: CatboxMemory (memory) is not suitable for production use! The cache will not be shared between each instance of the service and it will not persist between restarts.

Redis

Redis is an in-memory key-value store. Every instance of a service has access to the same Redis key-value store similar to how services might have a database (or MongoDB). All frontend services are given access to a namespaced prefixed that matches the service name. e.g. my-service will have access to everything in Redis that is prefixed with my-service.

If your service does not require a session cache to be shared between instances or if you don't require Redis, you can disable setting SESSION_CACHE_ENGINE=false or changing the default value in ~/src/config/index.js.

Local Development

Setup

Install application dependencies:

npm install

Development

To run the application locally:

1. Clone and run the backend service (https://github.com/DEFRA/fg-cw-backend) using CW_PORT=3001 docker compose up (Note: The backend service runs on port 3001 (not the default 3000))
2. run docker compose up redis
3. Once the backend is running, you can start the frontend application using the provided script

npm run dev

Production

To mimic the application running in production mode locally run:

npm start

Npm scripts

All available Npm scripts can be seen in package.json To view them in your command line run:

npm run

Update dependencies

To update dependencies use npm-check-updates:

The following script is a good start. Check out all the options on the npm-check-updates

ncu --interactive --format group

Formatting

Windows prettier issue

If you are having issues with formatting of line breaks on Windows update your global git config by running:

git config --global core.autocrlf false

Docker

Development image

Build:

docker build --target development --no-cache --tag fg-cw-frontend:development .

Run:

docker run -p 3000:3000 fg-cw-frontend:development

Production image

Build:

docker build --no-cache --tag fg-cw-frontend .

Run:

docker run -p 3000:3000 fg-cw-frontend

Docker Compose

A local environment with:

• Localstack for AWS services (S3, SQS)
• Redis
• MongoDB
• This service.
• A commented out backend example.

docker compose up --build -d

Running with fg-cw-backend

When running both the frontend and backend services together, port conflicts have been resolved by:

• Frontend localstack uses port 4567 (mapped to container's internal 4566)
• Frontend Redis uses port 6380 (mapped to container's internal 6379)
• Frontend MongoDB uses port 27018 (mapped to container's internal 27017)
• Frontend app runs on port 3000 (mapped to container's internal 3000)

To run both services:

1. Start the backend first:

cd fg-cw-backend
docker compose up -d

2. Then start the frontend:

cd fg-cw-frontend
docker compose up -d

You can then access:

• Backend API at http://localhost:3001
• Frontend app at http://localhost:3000

Dependabot

We have added an example dependabot configuration file to the repository. You can enable it by renaming the .github/example.dependabot.yml to .github/dependabot.yml

SonarCloud

Instructions for setting up SonarCloud can be found in sonar-project.properties.

Licence

THIS INFORMATION IS LICENSED UNDER THE CONDITIONS OF THE OPEN GOVERNMENT LICENCE found at:

http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3

The following attribution statement MUST be cited in your products and applications when using this information.

Contains public sector information licensed under the Open Government license v3

About the licence

The Open Government Licence (OGL) was developed by the Controller of Her Majesty's Stationery Office (HMSO) to enable information providers in the public sector to license the use and re-use of their information under a common open licence.

It is designed to encourage use and re-use of information freely and flexibly, with only a few conditions.