NOT Like a Rolling Stone

Where has the last year gone?  While life (metaphorically the stream in the hero image) rolls on, this blog (any of the moss covered rocks in the image) has not.

This blog was born of good intentions, but frankly it’s too hard for an old fart like me to remember how to maintain it and make contributions.  Having not posted here in many months, I had to consult my “documentation”, and ultimately my retired password manager, to get back in and post this.  That’s unacceptable, and it won’t happen again.  

Fixing Wieting Guild Pages

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

The last errors had this in common:

Searching for a Search Solution

A few months ago I sat in on a CFE.dev webinar and I was really impressed with what I saw. I made a note to come back and look closer at Pagefind, and my new blog – this blog that you’re presumably reading right now – really needed a search feature, so the “Search” box on this page (I hope it’s there) is the outcome.

Glad I Found Pagefind

So, I started looking closely at search options and considered things like Lunr, which I’ve used before, and Solr, which I both love and hate (because of its JAVA roots). Pagefind was, of course, also on that short list and it quickly solidified its position at the top of the list when I found Adding search to an Eleventy site by Mike.

Gating My Content

Gating Content in JAMstack Sites

This section’s title was borrowed from a Stackbit article with the same title, Gating Content in JAMstack Sites. Working through that article to password protect some of the content at https://Wieting.TamaToledo.com is my tech pursit today.

Nope, Not on Netlify

😦 Last evening I took a shot at implementing the Netlify Identity tricks from the aforementioned article, but could not easily get it to work. The problem, I think, is that the https://Wieting.TamaToledo.com on Netlify already uses Netlify Identity for authentication of my Netlify CMS forms, and adding a second, separate instance of that service isn’t trivial and perhaps isn’t even feasible. I also tried implementing some quick Staticrypt CLI protection but that also failed. Netlify does provide a really quick and painless solution, but it costs $20/month, at a minimum, to enable it.