Available on github : https://github.com/spboyer/ng2-kestrel-appserver Selecting the server architecture may or may not be a pivotal point in your application design...but it maybe it should. Micro-services, SOA, 12 Factor, ZDD and all of the other buzzwords do in fact have merit, getting away from the monolith application and "putting all of you eggs in one basket" server apps are a think of the past. Right? The core message here is "do one thing and do it well". So why would you couple your dynamic and static content into a single application? Static content doesn't change (often), scaling needs aren't 1:1 with the web api layers. However, there are some needs that the simple use of...
- Dipping the toe in the Azure Compute space and then some.
- Serverless like a Superhero with Azure Functions
- Use a container to show your function swagger
- Unmasking your swagger with proxies in Azure Functions
- Do more or less with default values in the Azure CLI
- Testing Azure Functions with Postman and Swagger
- Azure functions - Just the CLI, hold the GUI, add some git
- dotnet new angular to Azure with Docker using CLI
- Angular 2: Application Settings using the CLI Environment Option
- Troubleshooting Installing .NET Core 1.1 RTM on OSX
- Using Apache Web Server as a reverse-proxy for ASP.NET Core
- Deploying an Angular 2 App to Azure with Github
- ASP.NET Core: Watching Code
- .NET Core Slack Channel Sign Up