My wife wanted to start her own seeds this year but here in Maine, you have to do that inside and also make sure you keep the right temperature during the day and night. #RaspberryPiToTheRescue !!
Took a bunch of scrap pieces of wood that I had to make the bench itself so it doesn’t look pretty but it works. We just covered it with some painter’s drop-cloths to hold the heat.
Writing code for the cloud is great! So many positives that it just makes sense. The biggest downside with some is debugging your code….it gets tricky making a change, deploy, test then dig through your logs. Of course this can be automated but still get tiresome. With AWS enhancing their SAM (Serverless Application Model), it is now possible to actually run your lambdas locally within a docker container and have your IDE’s debugger attach. There are plenty of tools/plugins to utilize this (Eclipse, IntelliJ, Visual Studio…full list here) but I’m a big fan of Visual Studio Code. So let’s take a deeper dive in how to debug our java lambda line by line with VSCode!
My loving bride was able to get me another Pi Zero for Christmas! This is the 1.3 version with the camera slot. I decided to make it a little more capable by giving it a normal female USB slot and adding on a serial port so I can talk to it from any computer with a USB port. Nothing too fancy but makes it a little more usable so I can skip the OTG cable. Right now I just have a Wifi adapter hooked up to it with the connections already set…so if I’m at home or work, it will connect automatically and shoot me an email with the IP and then I can just SSH. Kinda nice. =)
So after many attempts following this post I finally got Visual Studio Code running on my Pi 3! Here is a breakdown of what I did.
You’re going to need to uninstall whatever version of Node you have so you can updated to the latest arm build: