Getting a "code to deployment" workflow is a story many organizations want to have nailed down when looking into new technology stacks and architectures such as ASP.NET 5 and the container story like Docker. I hear from business leaders comments like; "...that's great, but how do we deploy this, scale it. What does the development pipeline look like?" Great questions. For my own projects I wanted to be able to "just write code" and have the rest of the process handled. Not have to worry about how does it get built, deployed, scaled etc. Here is a working sample technology stack using all the cool kids on the block and some old players too. Setting It All Up The...
- 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