I have a raspberry pi configured to share my wifi internet through the ethernet port, so that I can turn my dump ethernet printer to a wifi accessible one.
I have started to use vim since a few months ago for all of the languages I use on my day to day development. On retrospective of good outcomes I hope to write a series of posts about how to setup your own vim configuration.
Saving a file with Angular is a bit tedius when we get the file as a blog from an API call. A traditional way of doing is to open the url in a new window. It can work unless there’s no authentication required by the API. In my situation though, the API validated authentication.
Last week I was configuring an end-to-end CI/CD pipeline using Teamcity, Angular/Cli and Octopus. Some of the pieces of this puzzle was not straight forward. So, in this post I am going to give you an step-by-step guide as to how I achieved it.
A development implementation of an Identity Server (found in almost all examples online) uses a Temporary Signing Certificate to sign the JWT tokens. A temporary key is created every time the identity server is restarted. A new signing certificate makes all the tokens generated before invalid. In a production environment however, you want the tokens to be valid after a re-deploy of the identity server. So the signing certificate should be constant. In this post I’d show you how to create and use such self signed certificates.
If you are using Identity Server 4 for authenticating an angular 2 or higher based web application, chances are you are using identity server implicit authentication flow. Means you are using browser redirects to grab the access token. In that case token refresh is done through a hidden iframe. In this post I am trying to show you how this could be done using Angular 2.
One of the problems of having an Identity Server behind a Load Balancer is to get the Discovery Document to show the correct urls. This post shows a solution with a custom Middleware to assign the proper url to the discovery endpoint.
Angular 2 now supports shallow testing with TestBeds. So we can create a Test Module just the same way we create a normal module, inject Test Doubles as services, or Spy on certain service functions to test Component + HTML both.
TypeScript debugging for Angular2 can be setup easily with few steps. We just need to configure the transpiler and debugger properly before launching chrome with debugging on. Let’s go in steps.
Unity is one of the widely used IOC containers. While using any IOC container, it’s always recommeneded to create only the instances that you need. But I have seen many below par unity configurations. In this article I hope to discuss different lifetime managers in order for us to better understand how they work.