Gameyfin (PostgreSQL + Scanner Stability Experimental Build)
This is an experimental community build of Gameyfin focused on improving:
- PostgreSQL compatibility
- bulk library ingest stability
- filesystem watcher behavior
- scanner resiliency under heavy workloads
Major Changes
Scanner / Watcher Stability Improvements
The original watcher/scanner pipeline struggled under large filesystem event storms (such as Nextcloud moving hundreds of game folders one at a time).
This build introduces:
- debounced scan scheduling
- queued scan deduplication
- safer scan lock handling
- reduced watcher-thread workload
- improved recovery behavior during large imports
Large ingest stress testing has included:
- repeated 200–1000+ game imports/removals
- Nextcloud-driven filesystem event spam
- PostgreSQL-backed metadata ingestion
- concurrent metadata provider workloads
PostgreSQL Support
This build contains ongoing work toward PostgreSQL compatibility.
This includes:
- PostgreSQL-compatible migrations
- Hibernate/JPA fixes
- concurrent entity creation fixes
- reduced transaction poisoning under parallel metadata ingestion
⚠️ PostgreSQL support is still experimental and under active development.
Important Notes
- This is NOT an official Gameyfin image.
- Migration/database behavior may still change.
- Always back up your database before upgrading.
- Some migration work is still being evaluated upstream.
Upstream Project
Original Gameyfin project:
https://github.com/grimsi/gameyfin