-
-
-
Scout Monitoring
Rennaisance engineers rejoice! 1 gem 5 min to app monitoring. 5-minute onboarding. No sales team. Devs in the support channels. No DevOps team required. Get the free app insights every engineer deserves with Scout Monitoring.
-
-
We wanted this machine to be as lean as possible. There is only so much memory and processing power to go around. Remember, our machine has 3 GHz Dual-Core Intel Core i7 processor with 16 GB 1600 MHz DDR3 memory. We also wanted as much of that space and power to be used for serving up our web applications. However, we also wanted to have an additional option for editing any code files, in addition to vim.
I've dabbled with containers and Kubernetes in the past, but have never run anything in a production environment. Since my container experience has been with Docker we're going to install Docker Desktop. It's the only option for installing Docker on a Mac. And, there's an option to also enable Kubernetes.
On the topic of directory structure we've kept our server very basic. To keep with Mac conventions we decided to keep all our files in the ~/Documents folder. For my son's projects we're going to be running the infrastructure with Kubernetes, so we named the directory for all his code phippy. With code cloned to our machine we wanted to have just a single GUI-based code editor. We chose VS Code.
In this post we're going to prepare the software to run our web server. As is the case when I set up most Macs, my first install is the Homebrew package manager. They have instructions on their site for how to install, and once you have Homebrew set up most of the rest of your software can be installed with a brew install in your Terminal. With the exception of our next piece of software.