The web frontend of the sc-tool. Uses the sc-tool backend.
The frontend requires node
to run. The version is defined in package.json
. For the frontend to work, it requires a running backend.
npm ci
to clean and install dependenciesnpm start
to run the frontend
variable | description | local value |
---|---|---|
VITE_BACKEND_SERVER | The url to the backend. | http://localhost:8080 |
VITE_PUBLIC_URL | The public url. | |
VITE_AUTH0_DISABLED | Disables the authentication. | true |
The deployment is being done via GitHub actions to the Azure.
The deployment is being done per stage. The table below shows the GitHub actions for the frontend, their descriptions, and triggers.
Name | Stage | Description | Triggers |
---|---|---|---|
deploy-test-swa.yml | Test | Deploys the frontend to the Azure TEST environment. | Push to main branch |
deploy-prod-swa.yml | Prod | Deploys the frontend to the Azure PROD environment. | Push to release branch |
deploy-infra.yml | Both | Deploys infrastructure using Bicep. | Manual |
Name | Description |
---|---|
AZURE_SC_TOOL_UI_TEST_TOKEN |
Test deployment token for azure static web app |
AZURE_SC_TOOL_UI_PROD_TOKEN |
Prod deployment token for azure static web app |
- As the frontend is tenant agnostic, a single frontend is being deployed per stage of the application.
- The routing from the frontend to the different backends is handled by Azure Front Door.