Cleaning up my Raspberry Pi

One thinks there’s only one problem, but then when one looks, here’s more than one. Here’s what needs to be done and what I have done before.

To Do

1. On the real PI, there is a problem with sudo, and it seems whatsnew I have written some new subroutines for whatsnew, but it doesn’t really take us forward. interestingly I could not get comm to work, so wrote my own. See if the sudo logs suggest anything, update the master version of whatsnew.
2. Might I need a new image for the Pi. If so, should I refresh the current one, buy a new one, or switch to AWS? I have a Pi 3, Model B Rev 1.2. Is there a version of the OS that is not hardware backward compatible, (looks like its OK, by Google Gemini), and how can I back up the system or just the web site and particularly the transmission files and configuration? The web site has a dev version, and I have backed its source up into a github repo.
   • if I rebuild the site, I should encapsulate it in a docker container, for which I need to learn how to install my certs, and run the service as a daemon.
   • and encapsulate the source in github repo, or download the theme from a github repo.
   • if I go with AWS, maybe I should move davelevy.info to AWS, the IONOS performance is not good.

My articles on Docker and Systemd are bing maintained. Below you’ll find, other article on this wiki, tagged “raspberry-pi”

To see the rest of what I have written, check out the HTML version of the feed which has more articles.