The following answers were accurate in late 2020:

When I accepted that in the real world you need to have a www subdomain, I was able to add it through AWS. I did not document that process, because AWS did a good job of explaining and it seemed to work perfectly. However, I later found out that it gave a security error in Safari. It said that my valid site may be spoofed. Therefore, I needed to add a www subdomain to my certificate.

Ran this from Technologytales 20190611:

>>>sudo certbot --expand -d existing.com,www.example.com
It worked, but it broke the automatic redirect from www.domain.com to domain.com that worked before. This is obviously an Apache problem, since www.domain.com brought up the default Apache page that lives on the server.

This error was fixed by using advice from Linuxize 20200101. I had to add their suggested code to two files (example.conf and example-le-ssl.conf).

Everything works, which is great, but someday, I would like to look at what I have with someone who understands Apache best practices. Plus, I should test the fix again after the cron job renews the certificate.

References
Technologytales_20190611_AddingNewDomainSubdomain_SSL_Certificate_Certbot
Linuxize_20200101_RedirectHttpHttpsApache

* Note - MySQL was from my notes, references lost

MySQL

select group_concat(distinct ac.animal_id, SEPARATOR ',') as animal_ids 
from animal_caretaker ac 
where ac.caretaker_id = 15 

Postgres

select string_agg(distinct cast (ac.animal_id as varchar), ',') as animal_ids
from animal_caretaker ac
where ac.caretaker_id = 15 
References
RoodtGreg_20190730_Coderwall_Postgres_GROUP_CONCAT

Taking off the slim from a Bootstrap 4 jquery link caused a bug. I was able to fix it, without losing the integrity, by putting the new url into the Hash generator.

Details: You use the Subresource Integrity feature by specifying a base64-encoded cryptographic hash of a resource (file) you’re telling the browser to fetch, in the value of the integrity attribute of any <script> or <link> element.

Details are directly quoted from MDN 20200528

References
user2761895_20180709_stackoverflow_HowGetIntgrity
SRI_HashGenerator
MDN_20200528_SubresourceIntegrity

To kill the process with pid==40676, you do this:

>> kill -9 40676
But if you know the port of a process, are not sure of the name and definitely don't know the id, then here's what to do:
>> lsof -i :8000

Where lsof means list of open files. The following is directly quoted from ss44: "An open file can be a regular file, a directory, a block special file, a character, special file, an executing text reference, a library, a stream or a network file (Internet socket, NFS file or UNIX domain socket.)"

The -i is a way of specifying an internet address. The colon says service or port.

>> sudo lsof -i :8000

The pid (40676 in this example) is displayed along with some other information

>> kill -9 40676

And it's done.

References
ghostdog74_20101004_stackoverflow_findKillProcess
ss64_bash_lsof