page_type | languages | products | description | urlFragment | ||
---|---|---|---|---|---|---|
sample |
|
|
This code is part of the Microsoft Learn module of the AKS workshop. It provides the frontend for the ratings application. |
aksworkshop-ratings-web |
This code is part of the Microsoft Learn module of the AKS workshop. It provides the frontend for the ratings application.
File/folder | Description |
---|---|
src |
Sample source code. |
static |
Data and images. |
.gitignore |
Define what to ignore at commit time. |
.dockerignore |
Define what to ignore at build time. |
Dockerfile |
Define how the Docker image is built. |
README.md |
This README file. |
LICENSE |
The license for the sample. |
To build this sample locally, you can either build using Docker, or using NPM.
- To build using Docker, in the project folder, run
docker build -t ratings-web .
- To build using NPM, in the project folder, run
npm install
- To run using Docker, run
docker run -it -p 8080:8080 ratings-web
- To run using NPM, run
npm start
Required configuration via environment variables:
- API:
<set to rating-api endpoint>
. This does not have to be publicly accessible. The application proxies the API requests via the backend to the rating-api endpoint.
The application exposes port 8080. You should then be able to access the application at http://localhost:8080.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.