I’ve been building other packages with QEMU, and I think we just blindly did it here, even though there’s no reason to use QEMU since Python is architecture-agnostic
Previously we were including the entire repo and using .dockerignore to exclude files and paths
I realized it’s easier to just have a path that represents most of the files within our Debian package, and we dynamically create a few more that need runtime information
Reached out to our engineering consultant partner for possible software projects for TinyPilot in areas we don’t know well
Customer support
Removed my direct email address from the TinyPilot website
The original idea was that customers interested in large orders could contact me directly, but that so rarely happens. Instead, it’s 99% users trying to bypass our normal support channels.
Updated instructions on the website for installing TinyPilot Pro
One of the support engineers discovered that the raspi-config has a non-interactive mode, so we could simplify our instructions by giving them a bash one-liner instead of a series of interactive steps.
Reviewed our internal playbook for handling corrupted filesystems