allsky-rodgau.de

After initially installing indi-allsky, I had experimented with various cameras, settings, and test recordings. Some of the time-lapse videos I’d created back then were long gone. However, the old entries still appeared in the video viewer, sometimes as black tiles without a preview.

I wanted to clean that up. But not by simply deleting everything before a certain date—rather, in a way that would leave productive footage untouched. In my case, I wanted the video archive to start only on or after December 23, 2025.

And here’s how I went about it…

By the end of 2025, I had set up a two-step backup process for my indi-allsky installation on the Raspberry Pi: First, I backed up the database, configuration, and migrations; then, the image files and time-lapses. This worked in principle, but over time it became significantly more time-consuming than necessary.

Now, the timelapses are also posted to my YouTube channel. I no longer want to transfer the large image collections to the FRITZ!Box over the local network every day. What’s much more important to me is that, in the event of an NVMe SSD failure, I can restore the running indi-allsky installation with as little effort as possible.

That’s why I set up the backup system anew in October 2026. The previous articles explicitly describe the old method: Phase 1: Database, Configuration, and Migrations, and Phase 2: Files and Quality-Based Backup. I’ve since disabled both cron jobs.

I recently deleted a few videos that had been uploaded to YouTube via the indi-allsky backend, but the indi-allsky video viewer still displayed “YouTube Uploaded” instead of the upload button.

Unfortunately, there’s no reset option in the backend for cases like this—but with a little coding and database know-how, the problem can be fixed.