This application was developed, for Hackney Council, to allow small businesses to apply for discretionary support grants during the 2020 coronavirus (COVID-19) pandemic.

It consists of a, publicly available, front end for applicants and a restricted back end for Grant Administrators to process claims.

Editable Diagram Source

The database engine is PostgreSQL, version 11 in AWS RDS.

Application submissions were closed at 2020-06-26T23:00:00.000Z. The front end reads an env var to enable this. The back end API blocks new submissions in pages/api/applications/index.js. In the event that applications are re-enabled, the back end should read the same environment variable.

If the application is re-enabled - when users upload supporting documents they will be stored in S3 with the wrong mime type set. See here for a complete description and fix.

This is a Next.js project bootstrapped with create-next-app.

The app needs Node 12, if you have NVM installed just run nvm use in your terminal.

Install the dependencies:

yarn install

Create your .env file from .env.sample. You will need to grab some secrets from (TBC, it's not clear at the time of writing, but you can view the environment variables on the Lambda if it is already running).

So that the auth token from using Staging/Production can work with your local dev environment and you will be able to access the admin section etc., add the following to your /etc/hosts file...

127.0.0.1       dev.discretionarybusinessgrants.hackney.gov.uk

Run the development server:

yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

1. Create the database:

   createdb dbg

2. Add the database URL as an environment variable in .env. On Linux you may need to provide a username and password.

cat <<<EOF >> .env
DATABASE_URL=postgresql://localhost/dbg
EOF

3. Run all migrations

   npm run dbmigrate up

To seed your database with data to get going quickly, you can run the file under db/seeds.sql by doing the following:

cat db/seeds.sql | psql dbg

Database migrations are managed with db-migrate. To create a new migration

npm run dbmigrate create description-for-your-migration

This will create an up and down migration as sql files in db/migrations/sqls as well as a javascript file in db/migrations to run the sql files.

Migrations are run with

npm run dbmigrate up

Migrations can be rolled back with

npm run dbmigrate down

You can do a dry-run to view the changes that will be applied without making any changes (for both up and down migrations)

npm run dbmigratedry up

To run database migrations against the RDS databases on AWS you need to run the dbmigrate up command via AWS System Manager.

1. Log into the AWS account
2. Go to System Manager
3. Go to Session Manager
4. Click 'Start Session'
5. Select an instance (there should only be 1)
6. Click 'Start Session' - This should open up a terminal like window in your browser
7. Run cd ~/discretionary-business-grants/ && git pull && npm run dbmigrate up

To seed the AWS database start as session as above and then run: cd ~/discretionary-business-grants/ && source ./.env && cat db/seeds.sql | psql $DATABASE_URL

Start a Session Manager session as above, then...

psql $DATABASE_URL

Currently this is created manually, which is not ideal. We could perhaps look at triggering a Lambda function to run the migrations, but that would not give us command line access to administer the database, so perhaps the Jump Box is best, in which case it should really be created with code (Terraform or CloudFormation), but in the meantime, these are the steps to recreate it manually.

• Create a new EC2 instance
  • Amazon Linux 2 AMI
  • t2.micro
  • same region/availability zone/subnet as the RDS database
  • The poorly named “bastion_profile“ role which has the correct Systems manager policy etc. and will come out the other end as "instance_role"
  • "Access to Postgres" security group
  • SessionManagerKey
  • Name “RDS Jump Box - Discretionary Business Grants"
• Then you probably need to add it to Systems Manager
  • Go to AWS Systems Manager Quick Setup
  • Client "Edit all"
  • Scroll to bottom and select "Choose all instances in the current AWS account and Region"
  • Click "Reset" and wait for the magic to happen
• Configure the instance
  • Start a new session via Systems Manager > Session Manager
  • Create SSH key

  mkdir ~/.ssh
  cd ~/.ssh
  ssh-keygen -t rsa -b 4096 -C "database-migrations-<environment>@jumpbox-<instance_id>"
  cat ~/.ssh/id_rsa.pub

  • Add SSH key as a deployment key on the repository
  • Install Git

  sudo yum install -y git

  • Install Node.js 12

  curl -sL https://rpm.nodesource.com/setup_12.x | sudo bash -
  sudo yum install -y nodejs

  • Clone the repository

  cd ~ && git clone [email protected]:LBHackney-IT/discretionary-business-grants.git

  • Install dependencies

  cd ~/discretionary-business-grants && npm install

  • Add the DATABASE_URL environment variable (you can get the database details from the Lambda environment variables)

  echo "export DATABASE_URL=postgres://<username>:<password>@<endpoint>:<port>/discretionaryBusinessGrantsDb" >> ~/.bashrc
  source ~/.bashrc

  • Install PostgreSQL so we can use the client

  sudo amazon-linux-extras install -y postgresql11