Buckinghamshire Council - HR Service Desk alpha
- nodejs version
This uses hot reloading to improve developer experience, but the site is run purely on the client side until it is built.
npm run dev
To build files to
npm run build
BUILD_CONFIG=staging|production|development (defaults to
development) environment variable should be used to define to the application the environment it is running in. This is separate to
NODE_ENV since many libraries (React included) rely on the de-facto standard values of
production|development to optimise their running.
NODE_ENV automatically accordingly in webpack.js.
No passwords / keys etc. are kept in the repo. Configuration is via AWS secrets and through env variables in Buddy.
We use a feature branch branching strategy - Gitflow:
- When a new feature is to be added, a developer should branch from
developnaming the new branch
feature/[userstory-id]-[short description of new feature for humans]
- When the work is ready (tested, linted etc.), a pull request should be opened against the
- A peer review should be made against the pull request and the branch subsequently merged.
- The CI server will build from the develop branch and deploy to the staging server.
Migration and API query tools available using contentful-cli.
||Start/end a CLI tool session|
||List all content types|
||Get a list of content type fields|
BuddyCI is used for the CI server.
BuildCI task validates all branches
Build & Deploytask runs whenever an update to
developis made. This task will update the staging server.
SSH / Keys
To give BuddyCI access to the integration server, the public key (found at
/environment-variables) should be added to the
~/.ssh/authorized_keys file on the staging server.