Sometimes you need to load data from an API before your Angular application can be initialized. I recently had such problem - in this case I had to get settings from the backend server. You may load the data in main component, but then it’s hard to make it available for all other components. It’s much better to hook into initialization process. Let’s see how to do it.
Last two posts were about docker and ASP.NET Core. Since my focus is now split between those two and Angular, I thought I would write a post about how to create a docker image with an Angular app. You will learn how to create an efficient Dockerfile, which will run tests and build your app using the Angular CLI.
In the last post, I have shown how you can build an ASP.NET Core app in the Docker container. Today I will introduce you to Docker Cloud - a service for orchestrating your containers. It’s working directly with Docker Hub (images registry) and is free for public containers. In the end of the post, we’ll have an application created last time running on the virtual machine, managed by Docker Cloud.
A few months ago I have started working on a new, greenfield, project. Since it’s a one-man job, it was crucial for me to have an easy setup without big dev-ops needs - especially in the early beta stage. I decided to use Docker because I could automate the building process using pipelines in GitLab and Docker Cloud for deployment. Today I would like to show you how to setup Continous Integration for an ASP.NET Core project using GitLab pipelines.
A few weeks ago, I have started to work on a new project based on ASP.NET Core. I quickly had to deal with problems I have already solved. Some of them I even described on this blog. I started to copy classes from other projects, but then I realised it would be better to make it opensource and available as a NuGet package. And that’s what I have done. Read on to see what utils are available there at the moment.