added reference links to readme

tweaked homelab and use-cases-for-lxd pages

README.md

@@ -1,5 +1,13 @@
 # Markdown source for radar231.com
 
+## References
+
+* https://www.mkdocs.org/
+* https://squidfunk.github.io/mkdocs-material/
+* https://guts.github.io/mkdocs-rss-plugin/
+
+## Info
+
 * This is the markdown source for the radar231.com website. It uses [MkDocs](https://www.mkdocs.org/) and [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/).
 
 * MkDocs is installed into a python virtual environment (venv). Then mkdocs-material and mkdocs-rss-plugin are installed into the mkdocs venv using the venv pip binary.

docs/posts/homelab.md

@@ -2,7 +2,7 @@
 hide:
   - navigation
 created: 2021-06-10 12:00
-updated: 2023-11-10 15:22
+updated: 2023-11-10 20:30
 tags:
   - HomeLab
 ---

docs/posts/use-cases-for-lxd.md

@@ -2,7 +2,7 @@
 hide:
   - navigation
 created: 2022-05-28 01:45
-updated: 2022-05-28 04:06
+updated: 2023-11-10 20:06
 tags:
   - LXD
 ---
@@ -40,7 +40,7 @@ After having used LXD for so many years at work, it only made sense to go all in
 
 As can be seen from the following screen capture, I have a number of LXD containers running. Some are acting as X86 nodes for my kubernetes cluster. There are currently two that are running as docker aggregation servers, where I run containerized applications that won't run correctly on the k8s cluster. I have a development system where I do my coding as well as ansible based management of the home lab servers. I also have one running Nginx Proxy Manager which manages internal access to applications running in either the kubernetes cluster or in docker containers within the home lab.
 
-[![LXD and Libvirt](../imgs/LXD-Libvirt.png){: style="height:25%;width:25%"}](../imgs/LXD-Libvirt.png){: target="_blank"}
+[![LXD and Libvirt](../imgs/LXD-Libvirt_sm.png)](../imgs/LXD-Libvirt.png){: target="_blank"}
 
 ## Conclusion