No cruft, let’s just start.Continue reading “A Shiny New Vuejs v3 Web App Using & Deployed to Amplify/AppSync/Cognito”
Over the years I’ve used Express.js many times as a quick getting started example app. Since I often reference it I wanted to provide a short post that shows exactly what I do 99.9% of the time to start one of these quick Express.js reference apps. I’ve detailed in this post how to get started with Express.js the fastest way I know. There is one prerequisite, I’m assuming in this post you’ve already got Node.js installed. With that in mind, check out my installation suggestions for Node.js if you need to get that installed still. The other thing, is you’ll need to have git installed. On MacOS and Linux git is most likely installed already, if you’re on Windows I’ll leave that googling exercise up to you.
Create a directory and navigate into the directory.
Now in that directory execute the following command. Note, this command is available as of node.js 8.2.0.
Inside that directory that you’ve navigated to, you’ll now have an Express.js skeleton app setup to run with the dependencies now downloaded with npm install. On MacOS or Linux run the following command to start the web app.
DEBUG=quick-start-express:* npm start
If you’re on Windows run the following command.
set DEBUG=quick-start-express:* & npm start
That’s it, one of the quickest ways to get a Node.js site up and running to start developing against!
If you’d like to dig in a bit deeper, here’s a great follow up post on creating APIs with Express. Give it a read, it’ll give you some great next steps to try out!
Cheers, and happy thrashing code!
UPDATED: April 4th, 2019 and again on March 17th, 2022
It seems every few months setup of whatever tech stack is always tweaked a bit. This is a collection of information I used to setup my box recently. First off, for the development box I always use nvm as it is routine to need a different version of Node.js installed for various repositories and such. The best article I’ve found that is super up to date for Ubuntu 18.04 is Digital Ocean’s article (kind of typical for them to have the best article, as their blog is exceptionally good). In it the specific installation of nvm I’ve noticed has changed since I last worked with it some many months ago.Continue reading “The Method I Use Setting Up a Dev Machine for Node.js”
But the project continued and persisted!
Today I TA’d (Teacher’s Assistant) a course with Bridget at GOTO Chicago Conference. There were a number of workshops besides just the Kubernetes 101 like; Working Effectively with Legacy Code with Michael Feathers (@mfeathers), Estimates or NoEstimates with Woody Zuill (@WoodyZuill), Testing Faster with Dan North (@tastapod), Data Science and Analytics for Developers (Machine Learning) with Phil Winder (@DrPhilWinder), and so many others that I’d love to have multi-processed all at the same time! Digging through Kubernetes from a 101 course level was interesting, as I’ve never formally tried to educate myself about Kubernetes, just dove in. My own knowledge is very random about what I do or don’t know about, and a 101 course fills out some of the gaps for me.
The conference is located in a cool and sort of strange place for a conference, out kind of in the lake, called the Navy Pier. Honestly, I dig it, it’s a cool place for a conference. I enjoyed the ~15 minute walk from the hotel to the location too, because it’s right there on the tip of the pier, as shown in the fancy map below.
The workshop is going well. Bridget is filling up student’s brains and I’m going to dork around Kuberneting some Cassandra and Node.js for my talk. I’m pretty stoked as the talk has given me a good excuse to delve into some Node.js again, from a nodal systemic viewpoint, “Node Systems for Node.js Services on Nodes of Systemic Nodal Systems” this Thursday.