manifest-prototype-base.yml

---

buildpack: python_buildpack
command: scripts/run_app_paas.sh gunicorn -w 5 -b 0.0.0.0:$PORT application
services:
  - notify-aws
  - notify-config
  - notify-template-preview
  - hosted-graphite
  - deskpro
instances: 1
memory: 1G
env:
  NOTIFY_APP_NAME: admin

applications:
  - name: notify-admin-prototype
Add config to deploy a prototype version of admin Sometimes we want to make changes to the admin app for doing user research that we don’t want all users to see (because we’re not sure if they’re the right changes to be making). Previously this meant doing the research using a team member’s computer, with the app running locally. This was bad for three reasons: - requires the time of someone who has the code running locally - requires the participant to use an unfamiliar computer - means the participant doesn’t have access to their own Notify account (or an account that we’ve set up for doing user research with) The dream* would be to have two versions of the frontend app running side by side in production. This commit makes the dream real – the two versions of admin are: - the normal admin app, accessible on `www.notifications.service.gov.uk` - a prototype version meant to be pushed to from a developer’s local machine*, on a `cloudapps.digital` subdomain Both of these apps share the same backing services, eg config, API instance, queues, etc, etc. Which means that the prototype version can be logged into with the same username and password, and the user will see their service and all their templates when they do so. Ideally this wouldn’t mean creating a separate base manifest. However it’s a feature of Cloud Foundry that you can override the application name. Which means a separate base manifest and a bit of duplication. 😞 actually the real dream would be to have a version of admin deployed for each branch of the admin app, but this might get a bit resource intensive. ** by running `CF_SPACE=preview make preview cf-deploy-prototype`, where `preview` is the name of the space you want to deploy to 2017-05-05 08:41:55 +01:00			`---`

			`buildpack: python_buildpack`
remove wsgi.py - always serve with whitenoise We're now running our app as a wsgi app locally, so don't need to distinguish between the two processes by having wsgi and application.py whitenoise just serves static files nicely - we don't lose anything by doing that locally. 2017-11-07 11:50:13 +00:00			`command: scripts/run_app_paas.sh gunicorn -w 5 -b 0.0.0.0:$PORT application`
Add config to deploy a prototype version of admin Sometimes we want to make changes to the admin app for doing user research that we don’t want all users to see (because we’re not sure if they’re the right changes to be making). Previously this meant doing the research using a team member’s computer, with the app running locally. This was bad for three reasons: - requires the time of someone who has the code running locally - requires the participant to use an unfamiliar computer - means the participant doesn’t have access to their own Notify account (or an account that we’ve set up for doing user research with) The dream* would be to have two versions of the frontend app running side by side in production. This commit makes the dream real – the two versions of admin are: - the normal admin app, accessible on `www.notifications.service.gov.uk` - a prototype version meant to be pushed to from a developer’s local machine*, on a `cloudapps.digital` subdomain Both of these apps share the same backing services, eg config, API instance, queues, etc, etc. Which means that the prototype version can be logged into with the same username and password, and the user will see their service and all their templates when they do so. Ideally this wouldn’t mean creating a separate base manifest. However it’s a feature of Cloud Foundry that you can override the application name. Which means a separate base manifest and a bit of duplication. 😞 actually the real dream would be to have a version of admin deployed for each branch of the admin app, but this might get a bit resource intensive. ** by running `CF_SPACE=preview make preview cf-deploy-prototype`, where `preview` is the name of the space you want to deploy to 2017-05-05 08:41:55 +01:00			`services:`
			`- notify-aws`
			`- notify-config`
			`- notify-template-preview`
			`- hosted-graphite`
			`- deskpro`
			`instances: 1`
			`memory: 1G`
			`env:`
			`NOTIFY_APP_NAME: admin`

			`applications:`
			`- name: notify-admin-prototype`