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.
For some time, I am using docker to setup my dev environment. If I need a database engine, I set it up as a docker container. Need RabbitMQ - docker. It is quite handy as you don’t need to install anything on your PC and easily remove it when you don’t need it anymore. Today, I wanted to setup ElasticSearch but turned out to be more complicated than simply executing a command found in the docker hub.
Nearly three months ago, I have joined a contest called “Daj Się Poznać” (Polish for “Get yourself known” or “Get Noticed”). The rules are simple - you have to blog twice a week and work on an open source project on GitHub. All of this for 3 months - from March till the end of May. As it is close to the finish line, I would like to give you an update on how I am doing so far.
We, as developers always strive to create most efficient implementations in our applications. We want fastest algorithms, multithreading and… async. Some say “async all the things”. This makes processes non-blocking. When one task waits for another one to finish, it’s not blocking resources. Some time ago, I have noticed similar patterns in the real life.