EFForg
Implement capture storage management in rayhunter-daemon
What problem does this feature solve or what does it enhance?
This comes out of PR #604. Currently, rayhunter stores its capture data in the same folder as the binary, and the installer uses symlinks to manage where this is. It would be better if rayhunter itself handled where to save the capture data, that way it can be changed dynamically and not just depend on where the binary is located. This would also allow rayhunter to handle swapping of SD cards, without losing the binaries or having to re-install.
Proposed Solution
Implement capture storage management in the rayhunter daemon. This should support the following:
- User facing options for recording destination
- Low/no storage alerts
- Monitoring of SD card presence (and auto switching?)
Alternatives Considered
No response
the storage path is configurable and not tied to the binary, though hidden in the UI. the config file path is hardcoded in init scripts
