This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4f8f01b
commit 2cae1f0
Showing
1 changed file
with
13 additions
and
165 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,171 +1,19 @@ | ||
| # nRF Asset Tracker Web Application for AWS | ||
| # nRF Asset Tracker for Azure firmware | ||
|
|
||
| [](https://github.com/NordicSemiconductor/asset-tracker-cloud-app-aws-js/actions) | ||
| [](https://github.com/semantic-release/semantic-release) | ||
| [](https://renovatebot.com) | ||
| [](https://mergify.io) | ||
| [](https://github.com/conventional-changelog/commitlint/tree/master/@commitlint/config-conventional) | ||
| [](https://github.com/prettier/prettier/) | ||
| [](https://github.com/typescript-eslint/typescript-eslint) | ||
| [](https://reactjs.org/) | ||
| [](https://getbootstrap.com/docs/5.0/) | ||
| [](https://github.com/css-modules/css-modules) | ||
| [](https://vitejs.dev/) | ||
|  | ||
| [](https://github.com/conventional-changelog/commitlint/tree/master/@commitlint/config-conventional) | ||
| [](https://github.com/nrfconnect/sdk-nrf/blob/main/.clang-format) | ||
| [](https://docs.zephyrproject.org/latest/contribute/index.html#coding-style) | ||
|
|
||
| The nRF Asset Tracker Web Application for AWS is a reference single-page | ||
| application (SPA) developed with [React](https://reactjs.org/) in | ||
| [TypeScript](https://www.typescriptlang.org/). | ||
| This repository maintains an out-of-tree **copy** of the | ||
| [Asset Tracker v2](https://github.com/nrfconnect/sdk-nrf/tree/main/applications/asset_tracker_v2) | ||
| application to show how to use open-source tools for automating the creation of | ||
| building HEX files, and continuously integrating the firmware against the cloud | ||
| implementation of the [nRF Asset Tracker for Azure](https://github.com/NordicSemiconductor/asset-tracker-cloud-azure-js). | ||
|
|
||
| The UI components are themed using | ||
| [Bootstrap 5](https://getbootstrap.com/docs/5.0/) and | ||
| [CSS modules](https://github.com/css-modules/css-modules). All complex UI logic | ||
| is extracted using [React hooks](https://reactjs.org/docs/hooks-custom.html) to | ||
| allow re-use when changing the UI framework. | ||
|
|
||
| [Vite](https://vitejs.dev/) is used as the frontend toolchain. | ||
| The copy is regularly updated from source and kept in sync with the NCS release | ||
| branches. | ||
|
|
||
| > :information_source: | ||
| > [Read the complete nRF Asset Tracker documentation](https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/). | ||
| ## Set up | ||
|
|
||
| npm ci | ||
|
|
||
| ## Configuration | ||
|
|
||
| In the | ||
| [nRF Asset Tracker for AWS](https://github.com/NordicSemiconductor/asset-tracker-cloud-aws-js) | ||
| folder, run `node cli web-app-config` and store the output in a local `.envrc` | ||
| file. Then run `direnv allow` to allow it. | ||
|
|
||
| ```bash | ||
| # .envrc | ||
| export PUBLIC_CELL_GEO_LOCATION_CACHE_TABLE_NAME=... | ||
| export PUBLIC_CLOUDFRONT_DISTRIBUTION_ID=... | ||
| export PUBLIC_FOTA_BUCKET_NAME=... | ||
| export PUBLIC_GEOLOCATION_API_URL=... | ||
| export PUBLIC_HISTORICALDATA_TABLE_INFO=... | ||
| export PUBLIC_IDENTITY_POOL_ID=... | ||
| export PUBLIC_NETWORK_SURVEY_GEOLOCATION_API_URL=... | ||
| export PUBLIC_NETWORKSURVEY_STORAGE_TABLE_NAME=... | ||
| export PUBLIC_USER_IOT_POLICY_NAME=... | ||
| export PUBLIC_USER_POOL_ID=... | ||
| export PUBLIC_USER_POOL_CLIENT_ID=... | ||
| export PUBLIC_WEB_APP_BUCKET_NAME=... | ||
| export PUBLIC_WEB_APP_DOMAIN_NAME=... | ||
| export PUBLIC_SENTRY_DSN=... | ||
| export PUBLIC_REGION=... | ||
| export PUBLIC_MQTT_ENDPOINT=... | ||
| ``` | ||
|
|
||
| ## Running | ||
|
|
||
| npm start | ||
|
|
||
| ## End-to-end tests using Playwright | ||
|
|
||
| The frontend provides [end-to-end tests](./e2e-tests) using | ||
| [Playwright](https://playwright.dev/). | ||
|
|
||
| ### Configure AWS credentials | ||
|
|
||
| The end-to-end tests run against an instance of the | ||
| [nRF Asset Tracker for AWS](https://github.com/NordicSemiconductor/asset-tracker-cloud-aws-js). | ||
|
|
||
| Either, use the credentials you created, when setting up the solution, or enable | ||
| the Web App CI feature and use the dedicated credentials created for this task. | ||
| The latter option is the recommended approach since it limits the permission | ||
| scope to only the needed ones. They can also be used to | ||
| [run the end-to-end tests on GitHub Actions](#running-end-to-end-tests-using-github-actions). | ||
|
|
||
| Add these environment variables to your `.envrc`. Then run `direnv allow` to | ||
| allow it. | ||
|
|
||
| ```bash | ||
| # .envrc | ||
| export AWS_REGION=... | ||
| export AWS_ACCESS_KEY_ID=... | ||
| export AWS_SECRET_ACCESS_KEY=... | ||
| export WEBAPP_STACK_NAME=... | ||
| ``` | ||
|
|
||
| ### Running the tests | ||
|
|
||
| You can then run the tests using | ||
|
|
||
| npm run test:e2e | ||
|
|
||
| ### Running individual tests | ||
|
|
||
| npx playwright test authenticated/map/locationHistory/gnss.spec.ts | ||
|
|
||
| ### Playwright Inspector | ||
|
|
||
| For developing tests it is helpful to run the | ||
| [Playwright Inspector](https://playwright.dev/docs/inspector). | ||
|
|
||
| You can enabled the inspector during the tests by running | ||
|
|
||
| PWDEBUG=1 npm run test:e2e | ||
|
|
||
| ### Running end-to-end tests using GitHub Actions | ||
|
|
||
| [This workflow](./.github/workflows/test-and-release.yaml) runs the end-to-end | ||
| tests for every commit. For this to work a running instance of | ||
| [nRF Asset Tracker for AWS](https://github.com/NordicSemiconductor/asset-tracker-cloud-aws-js) | ||
| is needed. The tests will be run against this instance. Typically it will be the | ||
| production instance, to ensure that the web application works with the current | ||
| production setup. | ||
|
|
||
| In order for the test runner to interact with the instance for retrieving the | ||
| app configuration and for providing test data you need to configure AWS | ||
| credentials as | ||
| [GitHub environment secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-an-environment). | ||
|
|
||
| Set these secrets: | ||
|
|
||
| - `AWS_REGION` | ||
| - `AWS_ACCESS_KEY_ID` | ||
| - `AWS_SECRET_ACCESS_KEY` | ||
| - `WEBAPP_STACK_NAME` | ||
|
|
||
| If you have enabled the web application CI of the nRF Asset Tracker for AWS | ||
| (`node cli configure context stack web-app-ci 1`) you can acquire them using the | ||
| nRF Asset Tracker for AWS CLI: | ||
|
|
||
| ```bash | ||
| node cli web-app-ci -s | ||
| ``` | ||
|
|
||
| You can set the secrets through the GitHub UI (make sure to create the | ||
| `production` | ||
| [environment](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment) | ||
| in your repository first). | ||
|
|
||
| Alternatively you can use the [GitHub CLI](https://cli.github.com/) using the | ||
| environment settings from above: | ||
|
|
||
| ```bash | ||
| gh secret set AWS_REGION --env production --body "${AWS_REGION}" | ||
| gh secret set AWS_ACCESS_KEY_ID --env production --body "${AWS_ACCESS_KEY_ID}" | ||
| gh secret set AWS_SECRET_ACCESS_KEY --env production --body "${AWS_SECRET_ACCESS_KEY}" | ||
| gh secret set WEBAPP_STACK_NAME --env production --body "${WEBAPP_STACK_NAME}" | ||
| ``` | ||
|
|
||
| ## Sentry | ||
|
|
||
| Optionally, Sentry can be enabled for the web application. Export the | ||
| `PUBLIC_SENTRY_DSN` environment variable. | ||
|
|
||
| To enable this in the continuous deployment pipeline of nRF Asset Tracker, | ||
| configure the DSN using the CLI: | ||
|
|
||
| ```bash | ||
| ./cli.sh configure thirdParty sentry sentryDsn https://4f901247818d46099a3f15b6ada9390e@o4504255385174016.ingest.sentry.io/4504684789170176 | ||
| ``` | ||
|
|
||
| When the next deployment is triggered, the DSN becomes available via | ||
|
|
||
| ```bash | ||
| ./cli.sh web-app-config | ||
| ``` |