GOV.UK Emergency Alerts admin application - https://admin.emergency-alerts.service.gov.uk/
- Register and manage users
- Create and manage services
- Author and approve emergency alerts
Ensure that you have first followed all of the local development environment setup steps, that can be found here, before attempting to run the Admin UI Server locally.
You can find instructions on specifying the correct Python version here.
If you don't have NodeJS on your system, install it with homebrew.
brew install nodenvm 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 useThe instructions on setting up the environment.sh file can be found here.
Please refer to the README in the /emergency-alerts-tooling repository, in the /emergency-alerts-tooling/compose folder.
For webauthn to work, the relying party URL must be equal to the domain, or be equal to a registrable sub-domain. The lower environments, preview and staging, have URLs matching the Route 53 DNS entries. However, production is a special case, so in /emergency-alerts-admin/app/webauthn_server.py, the production URL is defined as a sub-domain to prevent environment names being prefixed to the URL as with the lower environments.
The instructions for running the Admin UI Server can be found here.
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.
Current instructions for unit tests 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.