GitHub Continuous Deployment to a Raspberry Pi
GitHub Continuous Deployment to a Raspberry Pi
Instead of just using SCP to get files over to my device, I wanted to be able to have my Raspberry Pi update whenever there was an update to the master branch of the node project I was working on.
Join the DZone community and get the full member experience.Join For Free
Digi-Key Electronics’ Internet of Things (IoT) Resource Center Inspires the Future: Read More
So, I'm still playing with the Raspberry Pi while working on the wackcoon project (more to come on that) and I have the need to work in a group. Instead of just using SCP to get files over to my device, I wanted to be able to have my Raspberry Pi update whenever there was an update to the master branch of the node project I was working on. This would facilitate being able to work with a remote team (where the Pi is in my network) and, theoretically, if I had multiple wackcoon devices (although I have not thought about how to implement that yet.
To accomplish this, we will need the following.
- A GitHub hook on the repository
- A node app on the pi listening for messages from GitHub
- A way for the pi to be reached from the internet
In the Add webhook screen we need to add just a few things :
- Payload URL – This is where it will send the information to whenever events happen on your master branch. I will show you how I set this up in the next step.
- Content type – You can select application/json (what I am using) or application/x-www-form-urlencoded
- Secret (not required) – this is a secret you supply to verify on the sender
- Events – Which events you want to trigger this hook. The default is the push event and is what I am using for this example but there are many to choose from depending on your needs
NOTE: To learn about webhooks in depth, check out the documentation.
Fill out this information and click on Add webhook.
A Node App on the Pi
The next step is to set up an application on the pi that will receive the event. You can see what I have set up by looking at the wackcoon-hook project. All of the code is in the app.js file (check project for full code). It is a node site using express that has a route for a post on /payload. So for instance, in this app, it will be listening on http://localhost:5000/payload (yes… localhost, we will get to that in a minute).
So let's look inside my express route for post.
The first thing I do is look through the JSON that the webhook sent me for a couple of pieces of information (there is a ton, I will post an example at the bottom of this post, or look in the docs) I am just pulling out who did the push, and what repository they pushed to.
Next, after writing a simple message to the console, I am using a core node module called child_process that will allow me to run commands on the machine it is running on.
I call git, the folder I want to run it on, the command, and any flags i want. Since I might be using SCP to send files over the Pi when testing, I hard reset it, clean it, pull, and then do an npm install in case any modules were added (an added step could be to look through the JSON to see if the package.json was modified before running that last one, but I am not doing that), and finally running tsc since we are using typescript in the project.
Obviously, make sure you run this project on your pi using node app.js from the terminal.
Again, you can see, the entire project looking at the wackcoon-hook project.
A Way for the Pi to Be Reached From the Internet
Since this site is running on localhost, we need a way for GitHub to access this site. There are quite a number of ways for you to accomplish this. You could use port forwarding on your router to make it accessible to the outside world, or you could use one of two dev tools that I have used.
localtunnel – This is an npm module that will run on your Pi (or other devices) that allows you to set up a “tunnel” from your local port to a mapped URL that you can use point GitHub to. This is an opensource free npm module. I have used it but it is a bit flaky, it will shut down periodically and you have to re-run it. If you need help setting this up, here is a great tutorial to help you.
ngrok – This is a free tier, paid tier serves that, in their words helps you create “Secure tunnels to localhost” to answer the question ”I want to expose a local server behind a NAT or firewall to the internet.” If you need help with this, you can check out this tutorial.
That’s it, that is all you need. Now you can work as a team and have them push to your master branch on GitHub and it will automatically push it to your Pi. If you have any questions fell free to ask them in the comments.
As promised, here is the JSON that is sent from the webhook
Request URL: https://wackcoon.localtunnel.me/payload Request method: POST content-type: application/json Expect: User-Agent: GitHub-Hookshot/0b0c52f X-GitHub-Delivery: 7507b280-318c-11e6-9322-eaaef242aa6c X-GitHub-Event: push
Webhook – https://wackcoon.localtunnel.me/payload
Published at DZone with permission of Daniel Egan , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.