Introduction
Welcome back to the Creator Cloud series! We are thrilled to continue our collaboration with Scott from Alpha Nerd Tech, who is pushing the boundaries of what a compact home server can do for creative professionals.
In Part 1, we proved the concept with a single command. But let’s be honest—typing commands isn't exactly "workflow nirvana." In this episode, Scott takes us to the holy grail of data management: Full Auto Ingest. We are talking about a system where you plug in an SD card, walk away, and the ZimaBoard handles the rest. No apps, no clicking, no babysitting.
Let’s dive into how Scott turned the ZimaBoard 2 into an automated media appliance.
(Huge thanks to Scott for this incredible tutorial. Be sure to subscribe to Alpha Nerd Tech for more deep dives!)
The Dream: "No Chaos" Ingest
As a videographer or photographer, the last thing you want to do after a shoot is manually drag folders, rename files, and worry if you missed a clip.
Scott poses the ultimate question: "How amazing would it be to take an SD card, plug it into your system, and have your files already ingested, sorted by camera, and ready to edit?"
Today, we finish the job started in Part 1. The goal is simple: You plug it in, the system does the work.
The Architecture: Why Scripts Live with Data
Before we get to the magic, let's look at the file structure. On the storage pool, we have:
- CreatorCloud Folder: The root.
- Library: Where the sorted media lives.
- Logs: Proof of what happened (essential for trust!).
- Scripts: Where the automation logic lives.
Wait, why aren't the scripts in the OS?
If you are a Linux veteran, you might be used to putting scripts in /usr/bin. However, ZimaOS is immutable by design.
Tech Note: (Immutable means the operating system is "read-only" and locked down. This prevents system updates from breaking your custom setups and, frankly, protects you from accidentally breaking the OS.)
By keeping the scripts in the storage pool, the workflow survives updates, reboots, and even hardware swaps. The automation lives with the media, not the machine.
The Brains: Two Scripts to Rule Them All
To make this ZimaBoard setup fully autonomous, Scott uses two specific scripts.
1. The Auto Ingest Script (The Worker)
This script does the heavy lifting. It includes a "safety switch" to stop immediately if errors occur—no silent failures allowed.
It is smart enough to detect context. It looks at folder structures and file names to identify the camera brand:
- DJI: Looks for DJI_ prefixes.
- Canon: Looks for MVI_ or Canon folder structures.
- GoPro: Recognizes the specific DCIM layout.
- Sony: Identifies Sony XML structures.
Files are sorted automatically. If the script sees a DJI file, it goes to the DJI folder. If it sees a file it doesn't recognize? It goes safely into an "Unknown Camera" folder. Nothing is ever lost.
2. The Watcher Script (The Manager)
This is the piece that makes the system feel like a dedicated appliance. It runs in a loop every 2 seconds, scanning the system's "mount table" (the list of connected drives).
How it works:
- It checks for new devices mounted under /media.
- It explicitly ignores the ZimaOS system drive and the main storage pool (so it doesn't try to back up itself!).
- It uses a debounce timer. (This is a fancy way of saying it waits a few seconds to make sure the connection is stable before doing anything).
- Once confirmed, it triggers the Auto Ingest script.
The Live Demo: It Just Works
In the video, Scott performs a live test that is honestly beautiful to watch.
- He plugs in an SD card.
- Zero commands are typed.
- The system detects the card immediately.
The result? The script detected that the single SD card had been used in both a DJI drone and a Canon camera. It split the files, sending the drone footage to the DJI folder and the camera footage to the Canon folder.
He then swaps in a GoPro card. Boom. Detected, ingested, sorted into Video and Photo subfolders based on the date.
This is what calm ingest looks like. The ZimaBoard acts as a silent assistant, organizing your digital life while you grab a coffee.
What’s Next?
We have successfully built a "headless" ingest station. But the data is still just sitting on the server.
In Part 3, Scott will show us how to:
- Sync this library directly to a Mac Studio (or PC).
- Automate the delivery so files are ready to edit the moment you sit at your desk.
This little board has a lot more to give. Stay tuned!
Ready to build your own Creator Cloud? Check out the ZimaBoard 2 at shop.zimaspace.com and start owning your workflow.
