Bureaucrat, staff, administrator
477
edits
Changes
m
→Current Implementation
==Plan/Backlog==
# <s>Run a basic Express.js demo in a cloudlet node with a recent Node.js image </s> [DONE]# <s>Implement access to it from my new `dirks.nz` domain, using encryption (https) </s> [DONE]# Run Splunk in cloudlets '''[In progress]'''
# Implement a reverse proxy using library from npm (for traffic to/from above Express.js demo)
# Create Splunk HEC (Http Event Collector) (check if config persists through redeploys)
# Run the above suite in cloudlet and record results to splunk
# Schedule the above cloudlet to run daily
=Current Implementation=
==Express Demo Running in Cloudlets==
This step's objectives were to
# Standup a cloudlet node using an inbuilt Node.JS image
# Link it to my code repo [https://github.com/VincentDirks/node.js-in-the-cloud.git node.js-in-the-cloud]
# Access it from a subdomain of dirks.nz
# Implement encryption (https)
# Redirect calls to http to https, as well as any calls direct to the environment
The solution is accessible at https://nodejs-in-the-cloud.dirks.nz/
My code repo is [https://github.com/VincentDirks/node.js-in-the-cloud.git node.js-in-the-cloud]
A Git repo is added to the cloudlets Deployment Manager, deployed it to the Node.js container, with settings to monitor the repo for changes, so that the updates are fetched and container restarted automatically.
Created an nginx node to configure encryption and redirects
Using the cloudlets Let's Encrypt Free SSL addon to generate certs
fetch the changed nginx conf files and add to repo and update readme there to reflect
TBD
=Technologies=