(a) Create directory structure

Create a new top level directory clubSSG in your repo. Within this directory create the following directories: src, build and views.

Nothing to show here

(b) Copy clubProject site files

Copy your clubProject CSS and image files into the clubSSG/build directory. These are the files that won’t be processed by our program.

Copy your clubProject HTML files into the clubSSG/src directory. These will become the files that we will process and update.

Nothing to show here

(c) Update .gitignore

We are will be writing a Node.js program that will take the files of the src directory converting them to HTML files and placing them in the build directory. Add the appropriate line to your .gitignore file to ignore all the HTML files in the build directory. Show that line here.

(d) Convert src HTML to Markdown

Convert your HTML files into Markdown files that just contain content and metadata front matter. This can take some time. Also for HTML that doesn’t have Markdown equivalents you can mix in HTML, this can require some extra line breaks around HTML elements per the commonmark specification. Remember to add front matter for title and author.

Nothing to show here

(e) Templates

Add templates to the views directory for processing your content. Incorporate your navigation menu into your template via the <% include %> mechanism.

Show your base template here.

(f) Extend Program/Process Files

Now update your processIt.js program from homework #6 to process all the markdown files in the src directory to “generate” your static site. This program should list each of the files in the src directory to the terminal as it is processed.

Here is some code you can use for your dealing with files.

const fs = require('fs');
let srcPrefix = __dirname + "/src";
let bldPrefix = __dirname + "/build";
let allFiles = fs.readdirSync(srcPrefix);

console.log("Processing the src directory: ");
allFiles.forEach(function(srcName) {
    console.log('Reading ' + srcName);
    let fname = srcPrefix + '/' + srcName; // full name of the file to be read
    let fdata = fs.readFileSync(fname, 'utf8');
    //
    // Your file processing here
    //
    // create the full name of the file to be written change extension to .html
    let outName = (bldPrefix + '/' + srcName).replace(".md", ".html");
    fs.writeFileSync(outName, outString);
});

Show your code here.

(g) Deploy Your Site

Deploy your site to the department server. This is your last deployment of your static site. Put the link to the site here. All links and functionality from previous versions must work to receive credit.

(a) Get your Ethernet and IP addresses with Node.js

Using the program (netIf.js) given in the course slides Node/NPM Network Access obtain the IPv4 and Ethernet addresses for the computer you using to do this homework. If more than one network interface is listed make sure you choose the actual “external” interface that you are using. List these addresses here.

(b) Difference between Ethernet and IP

When we look at the diagrams of the Ethernet and IP packets in the course slides we see a number of similarities. Both contain source and destination addresses, a data payload, and a field to indicate what higher layer protocol the data payload is carrying. Why do we use IP for the worldwide Internet and only use Ethernet in limited networks? Answer here

(c) Packet size limits

Packets have size limits. These usually stem from physical layer considerations. Most Ethernet packets have a “maximum transmission unit” (MTU) of around 1500 bytes. How can we transmit an image on our website with a size of 200KB with this limitation. How would you solve this problem from a high level perspective? What network layer would you think should have this functionality? Answer here

(d) Difference between UDP and TCP

UDP and TCP both provide source and destination port numbers for “multiplexing” purposes. From an end user perspective what extra functionality does TCP provide over UDP and why do we use TCP to carry web traffic? Answer Here

(a) Who are your DNS servers?

Find out the default DNS servers your machine is using with the code below.

let servers = resolver.getServers();
console.log("DNS Servers:");
console.log(servers);

List these here, for the IPv4 addresses are any of these local to your network?

I get something like:

$ node dnsTest.js
DNS Servers:
[ 'fd56:a35c:a91::1', '192.168.1.1' ]

(b) Lookup the address of a domain name

Use Node.js and DNS to directly look up the IPv4 address of a domain. Please pick something interesting and unusual (not google or facebook).

// Use a different domain name here
resolver.resolve4('DrBsClasses.org').then((addresses) => {
    console.log('Address for DrBsClasses.org')
    console.log(addresses);
});

Show your results here I get something like:

Address for DrBsClasses.org
[ '73.158.236.89' ]