Save this file and run the validation command:
upload: timeout_seconds: 3600 # 1 hour max for 10GB files Never reuse temp directories across projects. The project new command automatically generates a UUID-based temp path, but verify with:
queue: redis: max_retries: 2 retry_backoff: "exponential" Even with perfect configuration, issues arise. Here is a cheat sheet for the most frequent problems: fileupload gunner project new
CONFIG SET maxmemory-policy allkeys-lru CONFIG SET save "" # Disable RDB snapshots during heavy uploads And in upload.yaml :
| Error Message | Likely Cause | Solution | |---------------|--------------|----------| | ETIMEDOUT: chunk write failed | Network instability | Increase chunk_timeout in upload.yaml to 60s | | disk full: /tmp/gunner_uploads | Temp storage exhausted | Mount a larger volume or enable streaming mode | | invalid project structure: missing gunner.workers.yaml | Incomplete initialization | Re-run fileupload gunner project new --force | | MIME mismatch: application/octet-stream | Strict whitelist blocking | Add application/octet-stream or improve client Content-Type header | | redis: CLUSTERDOWN | Redis cluster misconfiguration | Use a single Redis node for development, or fix cluster slots | Enable verbose logging: Save this file and run the validation command:
Whether you are a backend engineer, a DevOps specialist, or a full-stack developer, understanding how to implement, optimize, and troubleshoot a setup can save hundreds of development hours and prevent catastrophic data loss.
go run github.com/gunner-labs/fileupload@latest project new --output ./my-project Upon success, you will see a directory structure like this: go run github
npx gunner-cli project new --type fileupload --name my-upload-service Or if using the Go-based Gunner: