Get an account
Once your department, agency or team has an org account, you will need a personal account. Ask your org manager to authorise the creation of your personal account.
The GOV.UK PaaS is hosted in 2 independent regions, London and Ireland.
By default, the GOV.UK PaaS team creates new accounts in the London region unless you request otherwise during sign up.
To provide you with an account, we need to store some personal data about you. Please see our privacy notice for details.
Once you have a personal account, you can access the GOV.UK PaaS admin tool for either the London or the Ireland region (requires sign in). This tool allows you to view and manage your orgs, spaces and users without using the command line. Your level of access depends on your user role permissions.
Contact us by emailing firstname.lastname@example.org if you have any questions.
Set up the Cloud Foundry command line
GOV.UK PaaS is hosted on Cloud Foundry [external link]. You must use the Cloud Foundry command line interface (CLI) to manage your apps hosted on the GOV.UK PaaS. To set it up:
Download and install the Cloud Foundry CLI [external link] for your platform.
To check that it is installed correctly, run
cf -vin the command line.
If it has installed correctly, you will receive the
cf version X.X.X…confirmation message.
Depending on your network configuration, you might need to set an
HTTP_PROXYenvironment variable [external link] for the CLI to connect. Contact your network administrator for your configuration settings.
Sign in to Cloud Foundry. If your org is hosted in the London region, run:
cf login -a api.london.cloud.service.gov.uk -u USERNAME
If your org is hosted in the Ireland region, run:
cf login -a api.cloud.service.gov.uk -u USERNAME
USERNAMEis your personal account email address.
Enter the password you set during the sign up process.
When you are signed in, run
cf in the command line to see all available commands.
Deploy a test static HTML page
You can practice deploying an app by deploying a test static HTML page.
All orgs have a sandbox space for you to use when learning about the PaaS. When deploying a test static HTML page, you should target this sandbox space by running:
cf target -o ORGNAME -s sandbox
ORGNAMEis your org and
sandboxis the name of the sandbox space.
If you deploy an app using the same name and target as an existing app, the original will be replaced. If you are not sure about where to deploy your app, consult the rest of your team or speak to the PaaS team by emailing email@example.com.
In an empty directory, create an
index.htmlfile containing the following markup:.
<html> <head> <title>Static Site</title> </head> <body> <p>Welcome to the static site!</p> </body> </html>
manifest.ymlfile in the same directory as the
index.htmlfile. The manifest file tells Cloud Foundry what to do with your app.
--- applications: - name: APPNAME memory: 64M buildpack: staticfile_buildpack
APPNAMEis the unique name for your app. You can run
cf appsto see apps which already exist.
memoryline tells the PaaS how much memory to allocate to the app.
A buildpack provides app framework and runtime support. For example, if your app was written in Ruby, you would use the
ruby_buildpack. In this example, we use the
staticfile_buildpackfor the static HTML page.
In the directory where you created the files, run
cf push APPNAMEto push the static HTML page to the GOV.UK PaaS.
If you do not specify the app name in
cf push, the name specified in the manifest file is used.
The static HTML page is now available at your app domain.
For a production app, you should read the production checklist.