In this two-part series I’ll talk about: Part 1: Why to separate your configuration and code How to do it “in general” How to do it with an Azure App Service Some typical solutions for managing environment variables in the browser Part 2: Using environment variables with an Angular app served from an Azure App Service. Separating Configuration and Code Experienced developers recognize that a best practice for writing apps is to strictly separate configuration and code.
This post will explain how to set up a fully automated continuous integration/continuous deployment system for a node.js AWS Lambda Serverless service. This is the best way of deploying to AWS lambda if the code you’re using needs a native package (such as node-sqlite3 or better-sqlite3), because you’ll build your package on roughly the same operating system that powers AWS Lambda. However, this method is good to use for any AWS Lambda Serverless service.
Oh, which static site generator to use? I end up on staticgen.com all the time with my mouth watering. Jekyll, of course, has long been the top dog. It has the most mindshare primarily because Github Pages supports it out of the box. I’ve played around with Jekyll, and I’ve found it useful, and Ruby is always fun. For some reason I didn’t click with it, but for you it may be a good option.