6a6b3f78b1
Things we talked about: • asking users to write the number 'as numerals' or 'using digits' isn't very plain English • the style guide says to use an example in the error `..., like 5,000` but not if you have an example in the hint text, so we can't do that • I have reservations about 'correct format', because it sounds odd if you're not describing something like a phone number, NI number or credit card number. Looking back through Request to Go Live tickets on Zendesk. --- I got to September before I found anything that would count as invalid under our new rules: > Possibly around 1,000,000- not planning on implementing emails yet but might change I'll keep looking, but if most people enter the number according to the hint example we might be able to go with a much simpler error just prompting them to enter a number – no convoluted descriptions of what we mean by a number There seemed to be more problems when the Qs were about start volume and peak volume. Users felt the need to explain their plans more. Using 'number' instead of 'volume' is more explicit too – so that probably helps. In terms of errors: `Enter the number of emails you expect to send` `Enter the number of text messages you expect to send` `Enter the number of letters you expect to send` – will probably do it, right?
notifications-admin
GOV.UK Notify admin application.
Features of this application
- Register and manage users
- Create and manage services
- Send batch emails and SMS by uploading a CSV
- Show history of notifications
First-time setup
Brew is a package manager for OSX. The following command installs brew:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Languages needed
brew install node
NPM is Node's package management tool. n is a tool for managing
different versions of Node. The following installs n and uses the latest
version of Node.
npm install -g n
n latest
npm rebuild node-sass
The app runs within a virtual environment. We use mkvirtualenv for easier working with venvs
pip install virtualenvwrapper
mkvirtualenv -p /usr/local/bin/python3 notifications-admin
Install dependencies and build the frontend assets:
workon notifications-admin
./scripts/bootstrap.sh
Rebuilding the frontend assets
If you want the front end assets to re-compile on changes, leave this running in a separate terminal from the app
npm run watch
Create a local environment.sh file containing the following:
echo "
export NOTIFY_ENVIRONMENT='development'
export FLASK_APP=application.py
export FLASK_DEBUG=1
export WERKZEUG_DEBUG_PIN=off
"> environment.sh
AWS credentials
Your aws credentials should be stored in a folder located at ~/.aws. Follow Amazon's instructions for storing them correctly
Running the application
workon notifications-admin
./scripts/run_app.sh
Then visit localhost:6012
Updating application dependencies
requirements.txt file is generated from the requirements-app.txt in order to pin
versions of all nested dependencies. If requirements-app.txt has been changed (or
we want to update the unpinned nested dependencies) requirements.txt should be
regenerated with
make freeze-requirements
requirements.txt should be committed alongside requirements-app.txt changes.
Working with static assets
When running locally static assets are served by Flask at http://localhost:6012/static/…
When running on preview, staging and production there’s a bit more to it:
