Get started on GOV.UK
This is the guide for new technical staff working on GOV.UK in GDS. If you just joined, 👋 welcome!
Note that if you’re not working for GDS you’ll not be able to complete all of the steps in this guide.
You’ll need to use a Mac to follow this guide.
It will take you roughly one day to do everything in this guide from start to finish. There are lots of things to download, and loads of installers need to do their thing.
You’ll need up to 150GB of free space on your hard-drive to run the whole of GOV.UK.
Developing outside the VM
You don’t have to develop on the VM, but we strongly recommend it. If you have problems with the development VM you can always ask for help in the #govuk-developers Slack channel.
Where you should run commands
mac$ commands in the shell on your Mac:
mac$ echo "Think Different"
dev$ commands in the shell on the development VM:
dev$ echo "Linux for human beings"
If you run into problems
If you’re having trouble with Vagrant or the development VM, you can ask your colleagues or the #govuk-developers channel in Slack.
1. Install some dependencies
- git command line tool: either from the Managed Software Center or from git-scm
- The vagrant-dns plugin (
vagrant plugin install vagrant-dns)
Starting with High Sierra 10.13, kernel extensions must be approved by the user (see this Apple technical note). This causes the VirtualBox installer to fail with a permissions error.
To install VirtualBox on High Sierra 10.13 or later:
- Run the VirtualBox installer
- Open “Security & Privacy” in the system preferences
- Allow the blocked VirtualBox kernel extension
- Run the VirtualBox installer again
2. Create your GitHub accounts
- Set up a GitHub account.
- Ask somebody with access to add your GitHub username and SSH username (
firstnamelastname) to the user monitoring system.
- Ask your tech lead to add you to the alphagov organisation. You will have to be added to the GOV.UK team to get access to repos & CI.
- Generate and register an SSH key pair for your Mac for your GitHub account.
Import the SSH key into your keychain. Once you’ve done this, it’ll be available to the VM you’ll install in the next step.
mac$ /usr/bin/ssh-add -K your-private-key
Test that it all works by running
ssh -T email@example.com.
3. Create a user in integration and CI
User accounts in our integration and CI environments are managed in the govuk-puppet repository.
mac$ mkdir ~/govuk mac$ cd ~/govuk mac$ git clone firstname.lastname@example.org:alphagov/govuk-puppet.git
To create a new account, start by creating an SSH key at least 4096 bits long. For example:
mac$ ssh-keygen -t rsa -b 4096 -C "email@example.com" -f ~/.ssh/alphagov
Import the SSH key into your keychain.
mac$ /usr/bin/ssh-add -K ~/.ssh/alphagov
Now create a user manifest in
~/govuk/govuk-puppet/modules/users/manifests with your username and the public key you just created. Your username should use the
Create a pull request with these changes. Once it has been reviewed by a member of the GOV.UK team, you can merge it and it will automatically deploy to the integration environment.
4. Boot your VM
Run the VM bootstrap script:
mac$ cd govuk-puppet/development-vm mac$ vagrant up mac$ vagrant dns --install
This will take a little while, but it will throw up a question or two in your console so check back on it occasionally. Now might be a good time to scan through the GOV.UK technology blog while Puppet runs.
Once your VM is running, you can SSH into it with:
mac$ vagrant ssh
See the full command list by typing
Set your Git username and email
You can assign your name and email to commits on the VM:
dev$ git config --global user.email "firstname.lastname@example.org" dev$ git config --global user.name "Friendly Giraffe"
5. Set up your apps
Begin by checking out all of the GOV.UK services. There’s a handy shortcut:
dev$ cd /var/govuk/govuk-puppet/development-vm dev$ ./checkout-repos.sh < alphagov_repos
Most of our apps are written in Ruby and use Bundler to manage their dependencies. To boot apps, you’ll also need to install those dependencies:
There are also some Python apps, which use PIP. You’ll probably need to install those dependencies too, so run:
If installing the Python dependencies for fabric-scripts fails, your version of setuptools may be too old:
dev$ cd /var/govuk/fabric-scripts dev$ virtualenv .venv dev$ source .venv/bin/activate dev$ pip install --upgrade setuptools dev$ pip install -r requirements.txt
~/govuk/on your host machine is mounted as
/var/govukinside the VM. Any app repositories you clone should go here.
6. Access remote environments
Your pull request from earlier will hopefully have been merged by now. It’s time to test your access to servers via SSH.
If you’re not in the office right now, you’ll need to be connected to the GDS Office VPN for SSH access to integration.
While the applications are available directly via the public internet, SSH access to remote environments is via a ‘jumpbox’. You’ll need to configure your machine to use this jumpbox and use
govukcli to SSH into server.
- Copy the example SSH config file into the
~/.ssh/configfile on your host machine.
ln -s ~/govuk/govuk-aws/tools/govukcli /usr/local/bin/govukclion your host machine to be able to use the
govukclitool from any directory.
Test that it works by running:
mac$ govukcli set-context integration mac$ govukcli ssh backend
Next, follow the same steps inside your VM. You can choose whether to import your
alphagov keypair to the VM or to use the built in key-forwarding. Test that you can reach integration from your VM:
dev$ govukcli set-context integration dev$ govukcli ssh backend
7. Import production data
Dumps are generated from production data in the early hours each day, and are then downloaded from integration.
If you have integration access, you can download and import the latest data by running (replacing <2FA code> with the current 2-factor authentication code for AWS integration):
mac$ cd ~/govuk/govuk-puppet/development-vm/replication mac$ ./replicate-data-local.sh -u $USERNAME -F ../ssh_config -n
You will then be prompted to enter your MFA Token.
If you receive the error message
The config profile (gds) could not be found, refer to the guide about replicating data locally.
Once the data has been downloaded (if you don’t have integration access, ask someone to give you a copy of their dump), run:
dev$ cd /var/govuk/govuk-puppet/development-vm/replication dev$ ./replicate-data-local.sh -d backups/YYYY-MM-DD/ -s
For more information, and for troubleshooting advice, see the guide in the developer docs on replicating application data locally for development.
8. Run your apps
You can run any of the GOV.UK apps from the
/var/govuk/govuk-puppet/development-vm directory. You’ll first need to run
bundle install in this folder to install the required gems.
Since many of our apps depend on other apps, we normally run them using bowler instead of foreman.
To run particular apps with bowler, use:
dev$ bowl content-tagger
This will also run all of the dependencies defined in the
If you don’t need an optional dependency, you can pass the
dev$ bowl whitehall -w mapit
bowl commands fail, try the troubleshooting guide on how to fix a broken bowl.
Now visit this URL once the app is running:
You should be able to see Whitehall.
9. Keep your VM up to date
There are a few scripts that should be run regularly to keep your VM up to date. In
govuk-puppet/development-vm there is
update-bundler.sh to help with this. Also,
govuk_puppet should be run from anywhere on the VM regularly.
The following script will do all of this for you.
dev$ cd /var/govuk/govuk-puppet/development-vm dev$ ./update-all.sh
This will run:
git pullon each of the applications checked out in
govuk_puppetto bring the latest configuration to the dev VM
bundle installfor each Ruby application to install any missing gems
pip installto update runtime dependencies for any Python apps
10. Access the web frontend
Most GOV.UK web applications and services are available via the public internet, on the following forms of URL:
- http://publisher.dev.gov.uk (local dev, requires the application to be running)
- https://www-origin.integration.publishing.service.gov.uk (integration, HTTP basic auth)
- https://deploy.staging.publishing.service.gov.uk (staging, restricted to GDS office IP addresses)
- https://alert.publishing.service.gov.uk (production, restricted to GDS office IP addresses)
The basic authentication username and password is widely known, so just ask somebody on your team if you don’t know it.
If you can’t resolve
dev.gov.uk domains, see fix issues with vagrant-dns.