Skip to content

Commit

Permalink
Improve Heroku instructions (#32)
Browse files Browse the repository at this point in the history
The `http-server` we use within `npm run serve` accepts the `NODE_HTTP_SERVER_USERNAME` and `NODE_HTTP_SERVER_PASSWORD` variables by default, so by specifying these, there’s no need to edit the `Procfile`.
  • Loading branch information
frankieroberto authored Jul 11, 2024
1 parent b93bebf commit c6d21b2
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions docs/get-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,14 +116,11 @@ The process is very similar to [setting up a prototype on Heroku](https://govuk-

#### Password protect your design history

We’ve found it’s better to keep a design history public. But if you need to password protect yours, you can add a username and password using environment variables (Heroku calls these “config vars”):
We’ve found it’s better to keep a design history public.

- set `USERNAME` and `PASSWORD` environment [variables on your Heroku app](https://devcenter.heroku.com/articles/config-vars#managing-config-vars)
- update the [`Procfile`](https://devcenter.heroku.com/articles/procfile) in the root folder with the following content:
If you need to make yours private, you can add a username and password using “[Config vars](https://devcenter.heroku.com/articles/config-vars#managing-config-vars)” on Heroku.

```text
web: http-server --username $USERNAME --password $PASSWORD -p $PORT
```
From the Settings page, add 2 items with the keys `NODE_HTTP_SERVER_USERNAME` and `NODE_HTTP_SERVER_PASSWORD` and setting a username and password in the values (you can use the same phrase for both).

### Netlify

Expand Down

0 comments on commit c6d21b2

Please sign in to comment.