Release 5.4.5

Fixed 🛠️

• PR #88 Zilean: Add database connection timeouts 🐛 - Thanks @skeet70 🙏

Release 5.4.4

Changed 🔄

• Zilean: Update to dotnet 9 🔄
• Zilean: Update to support both Zilean.Scraper & Zilean.DmmScraper for older version of Zilean 🔄

Notes 📝

• Zilean: Only Zilean v2.1.0 and newer are supported due to dotnet update to version 9 🚨

Release 5.4.3

Changed 🔄

• Riven Frontend: Updated the name and location of the server-config.json file to server.json and to be transferred to the /riven/frontend/config directory on startup 🔄
• Re-enabled reaping of zombie processes 🔄

Release 5.4.2

Fixed 🛠️

• Issue #72 Zilean Permissions Issue 🐛

Release 5.4.1

Fixed 🛠️

• Issue #71 PostgreSQL Graceful Shutdown 🐛

Release 5.4.0

Fixed 🛠️

• Issue #14 Add Riven build process to Dockerfile ✨
• Issue #65 Zilean Enabled when ZILEAN_ENABLED=false 🐛
• Issue #66 Dockerfile pulls from Riven Frontend main branch vs. latest release 🐛
• Issue #67 Future releases for Riven Frontend and Backend will require an API Key 🐛

Added ✨

• Riven Backend: Added the Riven backend build process to the Dockerfile 📦
• Riven Frontend: Added the server-config.json to the be saved in /config and transferred to the Riven Frontend when using the API key 📦
• Zilean: Added the Zilean build process to the Dockerfile 📦

Changed 🔄

• Riven Backend: Settings are now loaded with or without the API key depending on the version of Riven used 🔄
• Refactor: Refactored the utils and version checks 🔄
• Utils: Added description to reaped processes 🔄
• Logging: Added thread lock to rollover 🔄

Notes 📝

• Future releases for Riven Frontend and Backend will require an API Key to be set 🚨
• With these changes, you can now use the latest development versions of Riven Frontend and Backend 🌙
• Use the RIVEN_BACKEND_BRANCH=release-please--branches--main and RIVEN_FRONTEND_BRANCH=release-please--branches--main environment variables to test the current development versions of Riven 🌙

Release 5.3.2

Fixed 🛠️

• Issue #60 Does not correctly handle deleted files in new Riven releases 🐛
• Issue #61 Riven Backend v0.16.0 Broke Settings Update 🐛
• Issue #62 Riven Frontend v0.14.0 Broke VersionFilePath 🐛
• Issue #63 Riven Frontend v0.16.0 Broke Frontend Build 🐛 - This may be a temporary fix...

Release 5.3.1

Fixed 🛠️

• Issue #59 Zombie dotnet Processes Accumulating Over Time 🐛

Release 5.3.0

Added ✨

• pgAdmin 4: Added system_stats extension to pgAdmin 4 for host system monitoring 📦
• pgAdmin 4: Added pgAgent extension to pgAdmin 4 for job scheduling 📦

Fixed 🛠️

• pgAdmin 4: Fixed the pgAdmin 4 config_local.py SSL settings 🐛

Changed 🔄

• RIVEN_BACKEND_URL: Linked to the Riven backend load_settings function. PR #57 Thanks @FunkeCoder23 🙏

Release 5.2.0

Added ✨

• pgAdmin 4: Added pgAdmin 4 to the DMB image for PostgreSQL management 📦 - Resolves Issue #49

Notes 📝

• pgAdmin 4 is enabled by setting the PGADMIN_SETUP_EMAIL and PGADMIN_SETUP_PASSWORD environment variables 🆔🔐
• The DMB PostgreSQL server is automatically added to pgAdmin4 Servers🗄️
• On the first access of pgAdmin 4, the DMB PostgreSQL server password will need to be set in pgAdmin 4 🗄️ - the default PostgreSQL server password is postgres or set with POSTGRES_PASSWORD 🔐
• To access pgAdmin 4, navigate to http://<DMB_IP>:5050 in your browser 🌐
• The pgAdmin 4 data is stored in the /pgadmin/data directory - though, not required to mounted to the host 📁
• The pgAdmin 4 config_local.py is stored in the /pgadmin/data directory and symlinked at startup 📝 - review the pgAdmin 4 documentation for additional configuration options 📚
• Backups of the PostgreSQL database can be made using pgAdmin 4 and are stored in the /pgadmin/storage directory 🗄️
• The following message can be ignored on initial startup: ERROR - PostgreSQL subprocess: relation "version" does not exist at character 75