More love towards Linux

My journey towards AZ solution architect needs more hands own with Linux. So, today (still on PTO and recovering from a medical procedure) I decided to find my old HP Envy 2008, the one which I had abandoned and install Linux - Ubuntu Desktop version.

The process took me an hour:
1. downloaded Ubuntu iso image
2. decided  to burn the image to a CD. If you would like to flash to a USB drive, there are a lot of applications available (https://unetbootin.github.io/)
3. Updated BIOS settings to load from the internal CD drive.

Fun time with Linux

After suffering a lot of chronic sinus issues, I had decided to do a sinus endoscopic procedure. After that I took a few days off from wok. Apart from fun times with my kids, I felt a little bored and started to play around with Linux as my first step towards AZ SA certification.

As the first step, I tried to install Centos on my laptop using Virtual box. Since its a new machine, I haven't installed Linux distro and planning to do that for the last few months.

When I opened virtual box, the 64 bit variant is missing and the below two steps bring back the 64 bit option.

1. enable Virtualization from the BIOS (based on the laptop model - for HP spectra series use esc key and F10.)
2. Turn off hyper V feature from windows features (turn windows features on or off)

More details can be found here - http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/#.XUmqVvZFzOZ

Adding certificate permission for app pool

Go to mmc, select local computer and add certificate snap-in. 



From the personal store, select the certificate, right click → Tasks → Manage Private Keys and add permission to IIS_IUSRS and IIS AppPool\app pool name

HATEOAS provider for ASP.NET Core

When comes to API maturity model there are two major models:

1. Richardson Maturity Model

2. Amundsen Maturity Model.


To attain RMM 3.0, an API defines resources, respect HTTP protocol and provide self discover able links to  other resources.


To attain AMM 3.0, the APIs are focused on the actions the API affords and consumers can take.


So, to reach maturity level 3, the API or resource MUST provide an action or a list of  actions a client can identify on that API at the run time. This translates to HATEOAS.


While doing some research on Hypermedia As The Engine Of Application State(HATEOAS), I came across some great HATEOAS providers for ASP.NET Core, but they didn't quite fit my need, so I created my own one.


You can read more details from my github page 


- https://github.com/ajopjo/AspNetCore.HypermediaLinks

Headless CMS .NET Core

Inspired from Soctt Hanselman blog:

Most of the traditional CMS systems are monolithic, UI, back end systems, admin tools..etc. Since the world is rallying towards REST, headless CMS systems are becoming popular (integrate content via APIs).

A Headless CMS is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via a RESTful API for display on any device.

So, if you are doing some projects using ASP.NET Core, the below are the few headless CMS frameworks:

• https://github.com/jamesej/lyniconanc
• https://github.com/ButterCMS/buttercms-csharp
•  https://github.com/umbraco/Umbraco-CMS (ASP.NET web site is based on this)
•  https://docs.squidex.io/architecture/01-overview

Git flow simplified

I always get confused when it comes to git flow - from where to branch and merge. So, I kept the below cheat sheet.

• A develop branch is created from master
• A release branch is created from develop
• Feature branches are created from develop
• When a feature is complete it is merged into the develop branch
• When the release branch is done it is merged into develop and master
• If an issue in master is detected a hotfix branch is created from master
• Once the hotfix is complete it is merged to both develop and master

pic courtesy -> https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow

.NET framework and ASP.NET , MVC and EF and WebAPI version cheat sheet