Jeena
2df588b957
FreshRSS was the only service with just a config.yaml: no auto-update script, no instance context, and no review examples. That left the classifier with no few-shot context, so every release would fall back to "manual", and the auto-updater had nothing to run. These files bring it in line with the other services so patch & feature releases can be applied automatically while real breaking changes (volume path moves, new required env vars) still surface for manual review.
20 lines
1.2 KiB
Text
20 lines
1.2 KiB
Text
action: manual
|
|
reason: The data volume path inside the container has changed. Existing volumes mounted at /var/www/FreshRSS/data will not be picked up. Admin must update docker-compose.yml to mount the volume at the new path before pulling the new image.
|
|
---
|
|
> [!WARNING]
|
|
> Major release with breaking deployment changes. Read the migration guide before updating.
|
|
|
|
Breaking changes:
|
|
* The data directory inside the container has moved from `/var/www/FreshRSS/data` to `/data`. Docker users must update their volume mounts in docker-compose.yml accordingly, or FreshRSS will not find existing data.
|
|
* The extensions directory has moved from `/var/www/FreshRSS/extensions` to `/data/extensions`. Update your volume mounts.
|
|
* The default SQLite database location inside the data directory has been renamed from `users/_/db.sqlite` to `users/_/freshrss.sqlite`. Existing databases must be renamed before first start, or FreshRSS will start with an empty database.
|
|
|
|
Migration steps:
|
|
1. Stop the container.
|
|
2. Update docker-compose.yml volume mounts to use the new paths.
|
|
3. Rename the SQLite database file inside the data volume.
|
|
4. Pull the new image and start the container.
|
|
|
|
Features:
|
|
* New article view layout
|
|
* Improved API performance
|