Work

I finally got done, moving the blog from Nikola to Hugo today. I already wrote about why I did it. These are a few more thoughts about what went into the endeavour; and some colophonesque details. One, really small hope, is that it will help me learn Go. The DevOps world that I now seek to enter, speaks Go. I also, now run two Go programs that are indispensible to me, Hugo and Miniflux. And being the control freak, that I am, I’d love to tweak them to just how I like it. Nikola did help learn me Python, after all. ...

Moved over from Nikola, to Hugo today. In two minds about what to do with all the old posts. Do I just shed them all, like I’ve done in the past? Or work to move them over? Maybe, tomorrow’ll bring clarity. In the meanwhile, this is a house under construction, y’all! Stuff does not work, stuff looks wonky, and stuff both, looks wonky and doesn’t work. I’ll be at it, on and off, over the next few weeks, trying to make this home. ...

That’s just it for now :) Am learning Go!

While building my work product on the fancy-schmancy M1 work Mac, I kept running into clang errors, when I did a pip install Turns out, PyCLD3 would not build. So I did it manually. This tip on Github did the trick We need brew installed. And then we run the following commands in a terminal … brew install protobuf #install protobuf # set various compiler flags export GRPC_PYTHON_BUILD_SYSTEM_OPENSSL=1 export GRPC_PYTHON_BUILD_SYSTEM_ZLIB=1 export CFLAGS='-I /opt/homebrew/opt/protobuf/include' export LDFLAGS=-L/opt/homebrew/opt/protobuf/lib # install pycld3 python3 -m pip install pycld3 And we’re set! ...

Update: 28/12/2021 The solution? Move off the 64 bit Raspberry Pi OS and install Ubuntu. Everything below is now just for history and context :) Every time I update my Pi, whether it be an kernel update or due to something goofy I do, it refuses to be accessible via ssh after it boots back up. And everytime I bring it back to my desk, it just works. And when I put it back into its niche, by the door, it continues to work. But inevitably, sooner or later, comes a reboot, and we’re back to being inaccessible. No ssh, no plex, no network. ...

Stuff for future Jason to take note, when he tries to redo his Huginn instance … I wanted a quick and easy way to install it, without messing up my base system much, so I chose the Docker route. Now, I don’t know the A or D of Docker, so these quick notes for me to remember in the future. I need to install Docker rootless, and bring it up as a systemd service. If I want persistent data, I should create a Docker volume. Create an env file to hold all the secrets that I want to pass to the container I need to run and create my huggins instance first, give it a name, pass the env file and also remembering to mount the volume at the place I need I can then start and stop the image with the name I assigned it. I need to then tag the image with a policy to restart automatically So everytime Docker comes up, it will start the container automatically. P.S. Subscribe to my mailing list! Forward these posts and letters to your friends and get them to subscribe! P.P.S. Feed my insatiable reading habit. ...