This is the Next.js app behind apps.skde.no and the API.
There is two long-lived branches in this repository: main
and develop
. All changes to main
will update apps.skde.no and verify.skde.no. All changes to develop
will update test.skde.no.
New features and changes goes into the develop
branch through a Pull Request (PR). Before these changes go into the main
branch, the webpage test.skde.no has to be checked for errors.
The develop
branch will then be merged into the main
branch with
git checkout main
git fetch origin develop:develop
git merge develop
git push
Changes directly commited to the main
branch (for instance new News posts) have to be merged into the develop
branch:
git checkout develop
git fetch origin main:main
git merge main
git push
Run the development server:
nvm use # To pick (and install) correct (major) version of node
corepack enable # To enable yarn > v1
yarn install
yarn dev
Open http://localhost:3000 with your browser to see the result.
In production we build static html files that we serve in an S3 bucket on AWS. To reproduce this locally you can
export NEXT_PUBLIC_API_HOST="https://prod-mong-api.skde.org" # Our API in production
yarn install
yarn export
npx serve apps/skde/out
Start up decap-server
:
yarn run cms
Run the SKDE web site (in another terminal):
yarn run dev
Open the admin page helseatlas/admin.
This repository is set up with a hook that will run linting on staged files when you commit. You will therefore often end up with the following error:
$ git commit -m "some message"
✔ Preparing lint-staged...
⚠ Running tasks for staged files...
❯ .lintstagedrc — 1 file
↓ *.+(js|ts|tsx) — no files
❯ **/*.+(js|jsx|ts|tsx|json|html|yml|yaml|css|md) — 1 file
✖ prettier --write [EACCES]
↓ Skipped because of errors from tasks.
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...
✖ prettier --write failed without output (EACCES).
husky - pre-commit script failed (code 1)
It might help running npx husky
(or yarn prepare
).