Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/defra/hapi-web-boilerplate
hapijs boilerplate govuk web project
https://github.com/defra/hapi-web-boilerplate
government govuk hapijs
Last synced: 6 days ago
JSON representation
hapijs boilerplate govuk web project
- Host: GitHub
- URL: https://github.com/defra/hapi-web-boilerplate
- Owner: DEFRA
- Created: 2018-09-13T10:42:16.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2022-11-28T12:29:57.000Z (almost 2 years ago)
- Last Synced: 2024-04-14T07:53:26.211Z (7 months ago)
- Topics: government, govuk, hapijs
- Language: JavaScript
- Size: 549 KB
- Stars: 9
- Watchers: 6
- Forks: 2
- Open Issues: 4
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
[](https://travis-ci.com/DEFRA/hapi-web-boilerplate) [](https://codeclimate.com/github/DEFRA/hapi-web-boilerplate/maintainability) [](https://codeclimate.com/github/DEFRA/hapi-web-boilerplate/test_coverage) [](https://greenkeeper.io/)
# (Enter service name)
(Description of the service)
# Environment variables
(Be sure to describe any environment variables here by maintaining a list like this)
| name | description | required | default | valid | notes |
|----------|------------------|:--------:|---------|:---------------------------:|-------|
| NODE_ENV | Node environment | no | | development,test,production | |
| PORT | Port number | no | 3000 | | |
# Prerequisites
Node v8+
# (Checklist)
Once you clone this repository you'll need to make a few changes before you're ready to start:
- [ ] Add service name and description to the README above
- [ ] Check over the content of the 404 and 500 error pages and tailor to suit
- [ ] Update the `package.json` with the name, description and any git urls and authors etc.
- [ ] Update the [views context data](/server/plugins/views.js#L39) to include the correct service and default page title
- [ ] Remove the .git folder in the root directory. This will cut the cord to this boilerplate repo.
- [ ] Update the build status badges to your new project
# Running the application
First build the application using:
`$ npm run build`
Currently this will just build the `govuk-frontend` sass but may be extended to include other build tasks as needed (e.g. client-side js using browserify or webpack etc.)
Now the application is ready to run:
`$ node index.js`
(You can delete the remainder of this readme once you're up and running)
## What is this?
A simple hapi-based enterprise ready govuk web application boilerplate.
Click here for a similar [api boilerplate hapi project](https://github.com/DEFRA/hapi-api-boilerplate).
Based on:
- [hapijs](https://github.com/hapijs/hapi) - The framework & core plugins like `joi`, `vision` etc.
- [standardjs](http://standardjs.com/) - Linting
- [govuk-frontend](https://github.com/alphagov/govuk-frontend) - Styles & macros
- [nunjucks](http://mozilla.github.io/nunjucks/) - Default template engine
- [npm-scripts](https://docs.npmjs.com/misc/scripts) - Build tool
- [pm2](https://github.com/Unitech/pm2) - Process manager
## Getting started
Clone this repo and run through the checklist above.
Check the server is running by pointing your browser to `http://localhost:3000`
## Project structure
Here's the default structure for your project files.
* **bin** (build tasks)
* **client** (client js/sass code)
* **server**
* **plugins**
* **public** (This folder is publicly served)
* **static** (Put all static assets in here)
* **build** (This contains the build output files (js/css etc.) and is not checked-in)
* **routes**
* **views**
* config.js
* index.js (Exports a function that creates a server)
* **test**
* README.md
* index.js (startup server)
## Config
The configuration file for the server is found at `server/config.js`.
This is where to put any config and all config should be read from the environment.
The final config object should be validated using joi and the application should not start otherwise.
A table of environment variables should be maintained in this README.
## Plugins
hapi has a powerful plugin system and all server code should be loaded in a plugin.
Plugins live in the `server/plugins` directory.
## Logging
The [good](https://github.com/hapijs/good) and [good-console](https://github.com/hapijs/good-console) plugins are included and configured in `server/plugins/logging`
The logging plugin is only registered in when `NODE_ENV=development`.
Error logging for production should use errbit.
## Views
The [vison](https://github.com/hapijs/vision) plugin is used for template rendering support.
The template engine used in nunjucks inline with the GDS Design System with support for view caching, layouts, partials and helpers.
## Static files
The [Inert](https://github.com/hapijs/inert) plugin is used for static file and directory handling in hapi.js.
Put all static assets in `server/public/static`.
Any build output should write to `server/public/build`. This path is in the `.gitignore` and is therefore not checked into source control.
## Routes
Incoming requests are handled by the server via routes.
Each route describes an HTTP endpoint with a path, method, and other properties.
Routes are found in the `server/routes` directory and loaded using the `server/plugins/router.js` plugin.
Hapi supports registering routes individually or in a batch.
Each route file can therefore export a single route object or an array of route objects.
A single route looks like this:
```js
{
method: 'GET',
path: '/hello-world',
options: {
handler: (request, h) => {
return 'hello world'
}
}
}
```
There are lots of [route options](http://hapijs.com/api#route-options), here's the documentation on [hapi routes](http://hapijs.com/tutorials/routing)
## Tasks
Build tasks are created using simple shell scripts or node.js programs.
The default ones are found in the `bin` directory.
The task runner is simply `npm` using `npm-scripts`.
We chose to use this for simplicity but there's nothing to stop you adding `gulp`, `grunt` or another task runner if you prefer.
The predefined tasks are:
- `npm run build` (Runs all build sub-tasks)
- `npm run build:css` (Builds the client-side sass)
- `npm run lint` (Runs the lint task using standard.js)
- `npm run unit-test` (Runs the `lab` tests in the `/test` folder)
- `npm test` (Runs the `lint` task then the `unit-tests`)
### Resources
For more information around using `npm-scripts` as a build tool:
- http://substack.net/task_automation_with_npm_run
- http://ponyfoo.com/articles/choose-grunt-gulp-or-npm
- http://blog.keithcirkel.co.uk/why-we-should-stop-using-grunt/
- http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/
## Testing
[lab](https://github.com/hapijs/lab) and [code](https://github.com/hapijs/code) are used for unit testing.
See the `/test` folder for more information.
## Linting
[standard.js](http://standardjs.com/) is used to lint both the server-side and client-side javascript code.
It's defined as a build task and can be run using `npm run lint`.