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...
- 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
- Angular 2: Application Settings using the CLI Environment Option
- ASP.NET Core: Watching Code
- .NET Core Slack Channel Sign Up
- Angular 2 : Continuous Integration to Azure using Codeship and the Angular CLI