Introduction In the previous article we saw how we could let the browser do the typescript compilation. I had today a very interesting chat with Louis Lewis and he provided me the missing pieces for transforming the skeleton-navigation app with a minimal effort to a full blown typescript app while preserving the systemJs module syntax. show me the code Here we go. the gulp-typescript compile task the most important difference is of course is kicking out babel as transpiler and using typescript instead:

##Introduction I have seen many attempts to introduce typescript into the aurelia development pipeline. Usually, what they have in common, is that they are are all quite involved and complex. I tried to work the other way around, based on the new jspm beta, and I’m proposing here an extremely simplified setup for working with typescript in aurelia. Note that I’m only focussing on a development experience. Hopefully, this example is interesting enough to trigger a discussion towards a better aurelia typescript experience.

Introduction Obviously, CRM apps aren’t built in 5 minutes. Luckily, the idea of this article is not to show you how to build a CRM application and our sample really hasn’t anything at all to do with a Crm app. What I want to show in this article, is that setting up everyting you need for building a full stack application ready to be enriched with any line of business scenario can be effectively done in 5 minutes.

What is Aureliauth Aureliauth is a token-based authentication plugin for Aurelia with support for popular social authentication providers (Google, Twitter, Facebook, LinkedIn, Windows Live, FourSquare, Yahoo, Github ) and a local stragegy, i.e. simple username (email) and password. Aureliauth is a port of the great Sattelizer library to ES6 and packaged as an Aurelia plugin. Other OAuth1 and Oauth2 than the above mentioned providers can be simply added by editing the extensible configuration file.

Project structure Take a look at following project structure: There is the client and server folder in the root. Some developers surround these with a additional src folder. I don’t see any direct benefit in doing that. Another observation is that the bower_components are stored under client/app. The reason is that bower components are really tied to the client, they are never used from the server project. This in contrast with the npm modules, which are used both by the server as well as the client.

##Introduction I’m learning Gulp and sharing here my progressive insights. I’m a big fan of a decent continuous integration approach and to foresee as much automation as possible in your application development workflow. All that makes that your can put on your thinking caps for the right purposes, namely thinking about the software your are building. Furthermore an approach of “Deploy early and deploy often” will enhance the relationship with your stakeholders.

##Introduction In this article I’ll explain how easy it is to configure automatic fail-over when using MongoDb as database server. I’ll present things in such a way you can easily do this yourself on a windows machine. ##What is fail-over? Data and the especially the availability of data is crucial for an application. So, it makes a lot of sense to ensure that in case your database server goes down, the whole data handling is automatically taken over by another server.

##Introduction In this article, we’ll start from a fresh Ubuntu server and get a .Net web api up and running. All this can be covered in this very post. We’ll use the source code from the previous post stored on github over here. ##Step 1: Provision an ubuntu server This is very easy and covered everywhere on the net. I’ll use a virtual machine on my local windows 8 laptop using Hyper-V, but you can create an instance on azure, DigitalOcean, you name it.

Introduction I have been working lately quite insensively in the Linux world. Time again for some .Net. Let’s see what happened in the mean time with AspNet Vnext and let’s explore a Katana based web api. But we will not completely leave the Linux world. We’ll use Mono and run the web api on an ubuntu server and use Docker. We’ll connect the web api to a database backend via Entity Framework 6.

##Introduction In the first episode, we did setup nginx for hosting a nodeJs app and applied an additional rewrite rule. In this post we’ll provide some additional rebustness. What we are missing, is a kind of process which monitors our app and which assures that the app stays up and running. Furthermore the process should also make sure that the app is started when the machine reboots. So, you could call this process manager a kind of supervisor and indeed, that’s what we need: supervisor.