- Notifications
You must be signed in to change notification settings - Fork0
Belton Historical Society website built on .NET
License
JasonWeinzierl/BHS.NET
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
TheBelton Historical Society website,built on ASP.NET Core, Angular, and MongoDB.
- .NET 8 SDK and Visual Studio 2022
dotnet tool restore
- Node.JS 24 and yarn
corepack enable
- MongoDB
- You must have access to an instance of MongoDB.
- Either use a free cloud offering or set up a local instance.
- Add a connection string named
ConnectionStrings:bhsMongo.- See the below section on Configuration for other required settings.
- Open the
src/bhs-web-angular-appdirectory in VS Code or other editor. yarnyarn start- Use the included VS Code launch profiles to attach the debugger.
This starts the angular development server onlocalhost:4200, but backend requests will not succeed.See the next section for starting up the backendso that the web host can forward requests to the frontend development server if not handled by other middleware.
Use the launch profile in Visual Studio, or
dotnet run --project src/BHS.Web/BHS.Web.csproj --launch-profile BHS.Web
This starts the web application server and forwards SPA requests to the frontend.Test the frontend application through the launched browser window.
Navigate to/api/swagger to use the Swagger UI.This does not require the frontend development server to be running.
See separate repository: [https://github.com/JasonWeinzierl/belton-historical-society-infrastructure]
This application uses Auth0;you must set up an Auth0 tenant with RBAC permissions matching those set up inStartup.cs.You must also add the configuration settings as mentioned below.
The required configuration settings are listed in themodules/web-apps/configs.tf fileof the separate infrastructure repository.These settings include authentication settings, database connection strings, API keys, etc.Without these settings, various features may fail to work locally.
The infrastructure lists the following resource, which is a required setting you need to run this application locally.
resource"azurerm_app_configuration_key""auth0_domain" {configuration_store_id=data.azurerm_app_configuration.bhs.idlabel=var.environmentkey="AUTH0_DOMAIN"value=...}
Based on this resource, create a setting namedAUTH0_DOMAIN with a value of your Auth0 tenant's domain.
You may add this setting either to your local appsettings.Development.json,user secrets, machine environment variables, command line arguments,or else create an instance of Azure App Configuration with these.
Repeat this step for every other resource of typeazurerm_app_configuration_key.
If using Azure App Configuration locally, each key must be labeled with nothing or elsedevelopment.Add the App Configuration's connection string to a setting namedConnectionStrings:AppConfig.
About
Belton Historical Society website built on .NET
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Uh oh!
There was an error while loading.Please reload this page.
Contributors2
Uh oh!
There was an error while loading.Please reload this page.