| page_type | languages | products | description | urlFragment | ||
|---|---|---|---|---|---|---|
sample |
|
|
Add 150 character max description |
update-this-to-unique-url-stub |
This is a replica of the Urlist website but re-architected to use Azure AppService to host the backend instead of using Azure Functions. The original project repository can be found here https://github.com/the-urlist
Please check here to view and read about the architecture.
- Vanity URL: is a descriptive, human-readable, an easy to remember URL that is typically created to simplify sharing a long and hard-to-remember URLs.
- Link Bundle: a bundle/list of URLs that the user associate with a vanity URL using the Urlist application.
Outline the file contents of the repository. It helps users navigate the codebase, build configuration and any related assets.
| File/folder | Description |
|---|---|
api |
The backend code base implemented using .Net Core. |
frontend |
The frontend code base implemented using VUE and Typescript |
deployment |
This folder holds deployment scripts to setup infrastructure. |
pipelines |
This folder holds YAML files to create Azure pipelines to deploy the project |
docs |
This folder holds relevant documenation about the project |
.gitignore |
Define what to ignore at commit time. |
CHANGELOG.md |
List of changes to the sample. |
CONTRIBUTING.md |
Guidelines for contributing to the sample. |
README.md |
This README file. |
LICENSE |
The license for the sample. |
You need to have the following available
- An Azure subscription
- Check out the API folder for backend prerequisites
- Check out the Frontend folder for frontend prerequisites
- Check out the deployment folder to setup the Azure infrastructure automatically.
- Check out the pipelines folder to create the needed pipelines to automate deployments and infrastructure updates.
Once the pipelines are setup and had successfully deployed the project, find your Azure Frontdoor endpoint and use it to test the website.
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 opencode@microsoft.com with any additional questions or comments.