Nodejs Book: Chapter 3

In this chapter of the Nodejs book, we implement the functionality of a directory listing for a file server. In the case that the path of a folder is requested and no index.html exists in that directory, then we read the list of all of the files in the directory, and render a page to be returned to the client.

Nodejs Book: Chapter 2

This this chapter of our Nodejs “book” we create a simple file server, that will interpret requests to the server as file paths. The server will then search through the public directory for static files and return them to the http client if they are found.

Nodejs Book: Chapter 1

This this chapter, we go over the basics of the deceptively simple “hello world” server in Nodejs. And go over some of the concepts into why the same message will be returned to the user no matter what url is requested.

Nodejs Book (Abstract)

In 2017 I wrote a small “book” about getting started with Nodejs as an HTTP server. The book has been sitting on my hard drive for the last three years, so I figured if there is nothing better to do with it, then I might as well post it to this blog. To post a bit of background to this book, I should probably explain some of my experience with Nodejs. In 2011 was a student in university getting into server-side programming and I was having trouble of managing the differences between client-side Javascript and server-side PHP. That’s when the first video with Ryan Dahl came out announcing Nodejs.

WSD IT Academia

We now have a dedicated page for WSD IT Academia, which can be found here: It describes what we educate, and provides a full list of the curriculum.


リモートワーク環境の構築サービスの内容 (1)会社側ネットワーク回線の導入 (2)OpenVPNの設定 (3)Windows10Proの導入 (4)仮想デスクトップの構築 (5)Skypeの設定 (6)WP(ワードプレス…

Concept Images for EmraJs

While I haven’t had a lot of time to be able to spend on investigating into Jaxer to be able to streamline the install process. I have had a chance to take some time in working on some concept images for the EmraJs logo and mascot. So I guess we should start with the important part, which is the mascot.

Creating a Signup flow

It might have been a good idea to use a VPS since it has allowed me to get some perspective on something I’ve been thinking about for the last few weeks, which is how to get people to sign up for your service and get started using the service. And what better way to learn from the best since the VPS services have a lot of innovation and funding and marketing to make them stand out and be easier to use than other services.

Looking for targets

Since I haven’t had a chance to do a lot of testing recently, I think I can go ahead and continue to look for aspects of the server-side application that can be removed or simplified. In terms of testing, I think could try using multiple Pi’s, and always have a working version on hand, so when things break I at least have something to fallback on to say, “no really it works, look”. I was thinking about maybe using KVM to create a virtual Pi for testing, but that requires setting up a new server, since I’m always paranoid about messing up the bridge-network connection and having to trouble-shoot the network so that it works again.