Quick note: When I first wrote this article, it was entirely meant for ColdFusion developers who were interested in learning Node. After talking to my buddy Brian Rinaldi, he felt it would be useful for folks interested in learning Node in general. So I changed the title and URL, but kept the rest of the text as is. I think he is right and if you’re doing web dev in any server-side language, I think this might be very useful helping you grok some of the peculiarities in how Node works!
fetch is a bit modern but you could have replaced that with any other HTTP call) but I was curious to see if there was a way to do within my static site built with Jekyll.
Hey folks! So obviously I’m taking this Azure Functions thing a bit slowly. Not that folks care (probably ;) but I’m 10 days away from having my older kids in school and my youngest in day care which means 9 glorious hours of quiet time in my home office to really churn stuff out. In this post, I want to talk about how you can write Azure Function code locally and deploy to Azure for testing.
Back when I ran this blog on Hugo, I built my own little stats script (A Simple Stats Script Hugo) to help me look at my blog at a high level. I converted to Jekyll a few months ago and recently I started work on rebuilding that support back into my site. What follows is my own little stab at creating a script to report on Jekyll-based blog content. All of the code I’ll show below is up on my GitHub repo for this site and I’ll share specific links at the end. This is just the beginning and I have some ideas for more stats I’d like to add, but I’d love to hear what you think so drop me a line below.
So technically I’m not really back at work. Last week I took the kids on a short vacation to Arkansas and this week (well early this week), my eldest is at orientation at the University of Alabama. His brother is doing a “sibling program” and the two year old and I are sitting in a hotel room slowly going stir crazy. Well he is. In my last post I had talked about the initial sign up experience with Azure Functions and creating my first serverless function with it via their tutorial. My plan was to continue along the tutorial which switches to the CLI but I found some interesting tidbits I thought I’d share.
As I mentioned a few days ago, I’m going to spend time this summer looking at Azure Functions. For my first look, I wanted to focus on what the sign up process was like. I already had an Azure account, but I wanted to start fresh just to see if things had changed or improved. One of the things I was concerned about specifically was the login process. While I’ve never sat down to document it precisely, I know I’ve had issues with logins on Microsoft sites before. Unfortunately, I ran into that again. It was frustrating, but I did get past it.
I’m going to make two mistakes in this post. Well, mistake may be too strong a word. In general, I try to refrain from making “plans” as I almost always start off by promising to do more than I end up accomplishing. The second mistake is laying out a plan right before I go on vacation. I’ve already been somewhat slow here due to personal reasons, but I was thinking about this today and I thought it would be good to lay out some plans while giving myself a good amount of time (hey, “summer” could also mean Australian time too, right?) to get it done.
Let me start off by saying that this isn’t necessarily the best Visual Studio Code extension out there and - frankly - it’s probably near the bottom. But it’s a beginning and probably the easiest experience I had building an extension yet. So what did I build?
This is something that has been sitting in my “To Write” Trello board for a while now and today I finally got around to building a demo. One of my favorite things to do with serverless is to build API wrappers. There are thousands of APIs out there, but many times you need to manipulate or change the data to make it more appropriate for your use. While you can do that on the client, it can be much more efficient to do so on the server. Of course, who wants to setup a server just to change an API when you can use a serverless function instead? Some examples of this are: