We are back with our LTM (Learning through Making) tutorials and ready to hit the ground running and write some real Node.js code! In this series, we will learn about Node.js in the context of creating IoT (Internet of Things) projects. We will build a “CPU Sensor” in this first project since CPU loading/utilization is a “sensor” we can measure, record, and ultimately stream to other locations. In future tutorials, we will harness the power of Node.js to interact with physical sensors that live outside of our computing environment. Continue reading
We’re back with our LTM (Learning through Making) series of Node.js tutorials and we’re gearing up and getting ready to write some code! We’ve learned how to build a Raspberry Pi from the ground up including Node.js, we’ve created a web server in Node without code, and we’ve even managed to get this web server on the Internet as a cool trick.
So how are we going to write Node.js code? There’s nothing that would stop us from simply jumping onto our RasPi and using the Leafpad text editor or even the nano console-based editor to write our code. I propose that we use some more robust tools in the form of an IDE (Integrated Development Environment) to help us along in our coding journey.
It turns out that the RasPi 2 and RasPi 3—in spite of the significant CPU/memory boost they offer over their predecessors—will run most IDEs a bit sluggishly and will be frustrating for any serious Node.js work. I offer here a creative alternative we will use to expedite the software development lifecycle and run the Node.js code natively on the Pi. Continue reading
In Create a Web Server in Node without any Code, we used the http-server npm module to create a web server and serve up files in record time. Today I will share a way you can take the web server you built and make it available beyond your local network and on the public Internet. This is pretty cool trick, but I recommend that you use this with caution as this will open up a hole in your router/firewall when you make your web server available to the world.
Once again, we are using Node.js and so this will work on a variety of platforms. I am focusing here on making this work in the context of Raspberry Pi which is an amazing little machine for IoT applications and everything else under the sun. Ok, let’s get rolling.
Log into your RasPi from a Windows system by launching a Windows Remote Desktop Connection. (Hit the Windows key on your keyboard and type Remote Desktop Connection to get started.) This method of remote connection works since we installed xrdp on the RasPi as part of our Beginners Guide to Installing Node.js on a Raspberry Pi 2. Of course, you can connect the RasPi directly to a monitor/keyboard/mouse or use other remote options such as an X Server and come in through Linux, Mac OS X, etc. too.
After you are in the RasPi, launch a terminal session and type the following:
$ sudo npm install -g localtunnel
This will install the npm package called localtunnel globally so it is available as a command anywhere on the RasPi rather than just in the current directory. The localtunnel package npm page summarizes the mission of this package well:
localtunnel exposes your localhost to the world for easy testing and sharing! No need to mess with DNS or deploy just to have others test out your changes.
Now that we have localtunnel installed, let’s see what kind of parameters it accepts. You will notice that we invoke localtunnel with “lt” which is the command that is created as part of the global installation.
$ lt --help Usage: lt --port [num] <options> Options: -h, --host Upstream server providing forwarding [default: "http://localtunnel.me"] -s, --subdomain Request this subdomain -l, --local-host Tunnel traffic to this host instead of localhost, override Host header to this host -o, --open opens url in your browser -p, --port Internal http server port [required] --help Show this help and exit [boolean] --version Show version number [boolean]
We see a very nice, simple help page. I’m going to use the single-character options (e.g. -p) instead of the long option parameter names (e.g. –port). Please note that you must use two dashes (–port) when using long option names rather than one dash in order for localtunnel to understand and honor the long option name parameters you are passing.
We first need to get our Web server back up and running so that we can make it available to the world. Launch a new terminal session (leave the other first terminal session open still) and enter the following commands:
$ cd Public $ http-server
This will make the index.html file and any other files you have residing in your
/home/pi/Public directory available to be served up by the web server.
Next, jump back over to the original terminal session you launched so we can get localtunnel working. Let’s tunnel through to our web server running on port 8080 and launch the local web browser to view our web server from the outside world. (You can follow along by reviewing the options that are listed in the help info above.)
$ lt -p 8080 -o
Fantastic! Upon launching the above command, we are assigned a random subdomain such as http://jxloprztp.localhost.me and we now have our web server available on the real Internet. Go to another machine besides your RasPi such as a laptop/desktop or cell phone so that you can see for yourself that your website has hit the big time and is available everywhere! 🙂
You can now hit Ctrl-C in the terminal window running localtunnel to break the tunnel connection. Pretty amazing technology, eh?
Local tunnel has some other options. For example, you can choose your own subdomain rather than being assigned a random subdomain. Let’s try that now:
$lt -p 8080 -s mypizzaweb -o
Assuming nobody is actively using the mypizzaweb subdomain, you can now navigate to it by typing “http://mypizzaweb.localtunnel.me” in your Web browser address bar.
Once again, be sure to hit Ctrl-C in the terminal window running localtunnel to break the tunnel connection. It’s the wild west out there.
That’s it until next time!
Follow Dave Johnson on Twitter to stay up to date on the latest tutorials and tech articles.
Welcome back! In a previous tutorial (Beginners Guide to Installing Node.js on a Raspberry Pi), we installed Node.js on a Raspberry Pi. We are now ready to continue our LTM (Learning through Making) tutorial series and build a simple web server without any code. While this tutorial is geared toward the RasPi, the instructions can be easily mapped over to other platforms such as Windows, Linux, and OS X. Let’s get started! Continue reading
In preparing for my upcoming tutorial which is a beginner’s guide to installing Node.js on a Raspberry Pi 2, I ran into an issue. After getting the RasPi is up and running on the network, I was not able to ping its hostname (raspberrypi, by default) from another machine and find it so I could connect to it through Putty, xrdp, VNC, etc. After all, I wanted to be able to run headless and disconnect the monitor, USB keyboard/mouse, and still connect to it from another machine on my network.
One option was to run
ifconfig on the RasPi and take note of the IP address for
eth0 (if connected through Ethernet) or
wlan0 (if connected through Wi-Fi). I could then hard code this IP address in the hosts file on the Windows (or other) machine. The problem is that the RasPi retrieves its IP address through DHCP by default from my local router at home, and this IP address is not guaranteed to remain the same. I could log into my router and note the static IP address range and reconfigure the RasPi to use one of these static IP address rather than DHCP. However, I am preparing a beginner’s tutorial and not all of my readers want to become Linux TCP/IP networking experts.
I discovered an elegant solution if you are trying to ping and connect to the RasPi from another Windows machine on the same network. Samba to the rescue! Continue reading