Changes
- Added a backend to manage the configuration
- Added a settings page to edit pelagica settings from the frontend (admin users only)
- Updated Docker image to use a
configdirectory instead of directly mapping theconfig.json
⚠️ Migration Guide (from 1.x.x)
If you are upgrading from Pelagica 1.x.x and are running it via Docker, you’ll need to update your volume mappings.
Version 2 no longer mounts individual config files. It instead expects a config directory.
Required actions
-
Remove old config file mappings
- Any volume mappings that point directly to
config.jsonorconfig.schema.jsonshould be removed.
- Any volume mappings that point directly to
-
Mount your config directory
- Map the directory containing your
config.jsonto/configinside the container.
- Map the directory containing your
Example
Old (Pelagica 1.x.x)
volumes:
- /mnt/user/appdata/pelagica/config.json:/usr/share/nginx/html/config.json
- /mnt/user/appdata/pelagica/config.schema.json:/usr/share/nginx/html/config.schema.jsonNew (Pelagica 2.x.x)
volumes:
- /mnt/user/appdata/pelagica:/configAfter updating the volume mapping, restart the container to apply the changes.