Check out my new TESTING page where I hope to continue testing new features. Also, be sure to have a look at my new HIKES site and especially some of the “highlighted” hikes that are listed in bold there.
Note that HIKES used to be a “section” here, but there are a lot of them so I made a site just for them.
This morning I started an experiment… clipping leaves (“lobes” might be a better term for these things) from a healthy, indoor Sempervivum tectorum. What’s that, you ask? The common name is Hens and Chicks.
A couple of weeks ago I bought an on-sale strawberry pot full of Sempervivum tectorum and I have it growing on a little table on the front porch. It’s doing QUITE WELL there! A couple of days ago I uprooted a 3 foot square patch of Snow on the Mountain from a spot in my front flower beds (outside out southeast bedroom window), and that left a big bare patch of soil to be dealt with.
Now I’m going to try and get the component Simple_CRuD_Blog_App_with_Streamlit working locally as a proof-of-concept. Since I can’t “clone” the single project repo, and a “sparse checkout” seems wasteful since I’ll never push back to the original project, I’m going to git init an entirely new local named simple-CRuD-blog-app-with-streamlit and just copy/paste the contents.
Just the other day I got an updated copy of the Wieting Theatre’s volunteer roster and assignment schedule. As I’m trying to post them to the theatre’s management website (it’s password protected) I keep having issues with npm and dependencies that won’t compile. The fix, thus far has included a local command stream like this:
cd wieting-guild-pages
git pull
code .
npm run build
npm run start
--> failed
npm update
npm audit fix
npm run build
npm run start
--> failed
npm audit fix --force
npm run build
--> failed
npm install axios
npm run build
--> failed
npm update
npm run build
I’ve got Mackenzie looking at Streamlit as a means of building a mobile-friendly app that I can use to create posts like this one. That app will need to allow me to edit a TITLE and Markdown BODY fields, capture location and time, and post all of that information to my personal blog… preferably from my cell phone. I’ve captured some possible resources and guidance in https://www.one-tab.com/page/71iaDADxT-eLEOx15qeVnQ.
Elementary School Weed Control
Went to the elementary early this evening and sprayed Weed-B-Gone around the bench and area. I hope it knocks the remaining weeds there back. There was no wind and no rain thus far, so I hope it works.
Geowoodstock 2023 (GC89GMX) and Kentucky’s oldest surviving geocache (GC39E) were the intended destinations of another epic roadtrip with gossamar on May 25-28, 2023.
The route and cache count looked something like this:
The green lines represent my “outbound” route while the red lines show my “return” route back from GC39E. The ordered list of caches and events found is available for download below.
Staying this weekend in a Marriott in Owensboro, Kentucky, for GeoWoodstock 2023. Headed to Louisville in the morning for some oldies.
Cyclone 1965 Completed
This morning I was dealing with the 1965 edition of the Grinnell College yearbook, Cyclone 1965, in Digital.Grinnell. That’s a monster of a yearbook, 278 pages and a .pdf that’s almost 1.4 GB in size.
In order to get the .pdf to upload I tried a number of tricks, the only one that worked was a modification of Book Ingest in Digital.Grinnell The key command was…
So, node and npm seem to be all the rage these days, and perhaps for good reason. I recently fell in love with Eleventy/11ty over Hugo because it’s Javascript, not Go, and it’s elegantly simple with tons of flexibility. I recently tried to add Pagefind search to a Hugo static web site (see https://static.grinnell.edu/dlad-blog/posts/143-significant-rootstalk-retooling/). If Rootstalk, an Azure Static Web App was framed in node.js, as both Eleventy and Pagefind are, there would be no problem. The Azure scripts used to deploy those frameworks are far more customizable than Hugo, and there’s documentation to prove it.
