Yesterday I shifted my data and setup from the Pi5 8gb to the Pi5 4gb with relative ease. I rsynched the data from one Pi to the other, brought up the docker containers, checked that they were working before shutting down the other Pi. I then swapped the 8gb Pi with the four gb pi and turned on the four gb Pi, after plugging the hard drive that I use to store photos and audiobooks and podcasts.
There are several types of people. One of them is youtubers that try and fail until they succeed, and then there are people like me, who also try and fail until they succeed. In one case the individual probably gets millions of views, and earns enough to waste hundreds of dollars per video in microtransactions, to people like me who are experimenting with Pis because it’s cheaper, once you know what you’re doing than getting a synology box.
This morning I made PhotoPrism self-booting. I am not certain that this is the write term so I will specify what I mean. PhotoPrism, when run via docker boots, when we tell it to boot, like any other app on our laptop. This morning, after a little time spent with AI I found the solution.
I used ChatGPT for this help but this is to give you an idea of how to enable docker containers to boot automatically rather than manually.
Yesterday I configured PhotoPrism to work with my iPhone photo album that was being synced to Infomaniak’s Kdrive, before then being synced to a drive that I could access via the Photoprism docker-compose config file. I then used No-ip to make that PhotoPrism instance available to the world wide web.
For several years I have had an Infomaniak Kdrive account but did not use it much, until I noticed that what costs 100 CHF with Google Drive costs 67 CHF with Kdrive.
Last night I spent hours going through videos and changing them from “public” to private, so that they would be removed from the index. I went through them by loading 2024 without filters and worked my way through 60 or so files at a time, before scrolling, and waiting for content to load. After a few hours I got bored so tried to switch things up.
I decided to sort images by camera but that’s slow, so I tried to sort by colour, and by category, and more.
After more than a week of working twenty four hours a day my Raspberry Pi 4 finally indexed over 120,000 videos and photos. The first thing that I notice is that Photoprism feels slower now. It takes several seconds and it feels as if it is suffering.
Overloaded with 120,000 Files The Raspberry Pi 4 and PhotoPrism were not designed to have so many photos at once. It tells me that 63,000 files are videos, which I will remove from this archive eventually.
A Cold Walk Yesterday I went out for my daily walk but within minutes I noticed that my legs felt cold and that I really did need the scarf that I wore. It’s exceptional for me to wear a scarf. My fleece and my inner coat both have neck protection built in so I usually feel fine. Yesterday was unusually cold so I was happy to add the scarf to really keep my neck warmer.
Yesterday I started the proper migration of my Google Photo assets from Google Takeout to PhotoPrism. The first step was to mount the drives to the linux system, the second was to transfer the photos from the external hard drive to the internal SD card, unzip them, and then start imposing assets.
The first bottle neck is exporting 800 gigabytes from Google drive to a local drive. I chose to download the files in one gigabyte packages in fifty gigabyte sets over many hours.
Last night I installed Immich on an HP laptop with ease. The issue I came up against is that laptops sleep and hibernate after a few minutes unless you are actively using them. This means that you need to use them whilst files are being transferred if you do not want tasks to be interrupted. That’s why, this morning I decided to try installing immich on two different raspberry Pi devices.
While playing with Nextcloud I found a serious flaw. If you add images via the command line from one directory to another, and then delete them, then their ghosts remain in the timeline. By ghosts I mean references to these files in the CMS and there is no quick way of removing them. You need to remove them individually and that’s time consuming. That’s why, when I was trying to find a solution I came across Photoprism.