Website for emergency alerts, hosted under /alerts on GOV.UK.

• Preview (in GOV.UK Integration) (ask in Slack for credentials)
• Staging (in GOV.UK Staging) (needs VPN)*
• Live (gov.uk/alerts)

* Note that, even when connected to the VPN, you may see a 403 Forbidden page due to an issue with the way GOV.UK Fastly is configured with Fastly shielding.

Ensure that you have first followed all of the local development environment setup steps, that can be found here, before attempting to run the gov.uk/alerts locally.

You can find instructions on setting the correct Python version here.

If you don't have NodeJS on your system, install it with homebrew.

brew install node

nvm is a tool for managing different versions of NodeJS. Follow the guidance on nvm's github repository to install it.

Once installed, run the following to switch to the version of NodeJS for this project. If you don't have that version, it should tell you how to install it.

nvm use

To compile and run the project you need the following

brew install proj
brew install geos

• If pre-commit is not already installed on your machine, run brew install pre-commit

• In this repository’s folder, run pre-commit install and pre-commit install-hooks

The instructions to run the gov.uk/alerts server can be found here.

We aim to match the browsers supported by GOVUK Frontend (includes Internet Explorer 8-10).

Any Python code changes you make should be picked up automatically in development. If you're developing JavaScript code, run npm run watch to achieve the same.

This app can also be run as a Celery worker, but this is currently broken on some machines. See #214

The instructions for running the unit tests for gov.uk/alerts server can be found here.

To continuously run js tests, run npm run test-watch.

To run a specific JavaScript test, you'll need to copy the full command from package.json.

• Architecture
• Image optimisation
• Setting up redirects
• Updating dependencies
• JavaScript documentation