Is this a new feature request?
Wanted change
Linuxserver images need a new volume mount for persistent plugin storage - most likely this is a documentation change.
Reason for change
I've added a new plugin system to Manyfold (coming in v0.146.0). In order to last between container updates, the plugins need to be stored somewhere persistent. I've added a PLUGINS_PATH environment variable which defaults to the app's plugins directory, but it needs persistent storage mounted at that location, which I've mentioned in our example dockerfile (see manyfold3d/manyfold#6569).
Proposed code change
The app will work without persistent storage mounted, and should show a warning on the plugin screen if it's not writable, so nothing should break; however, I imagine you'll want to add how users should set this up in a linuxserver way in your docs. Normally I'd do a PR myself, but I don't want to make assumptions on what you want your users to do.
As an example, in our single-container "solo" image, I've preconfigured the path to /config/plugins, as there's already an SQLite database at /config and users will already have a volume mounted there that we can use.
Is this a new feature request?
Wanted change
Linuxserver images need a new volume mount for persistent plugin storage - most likely this is a documentation change.
Reason for change
I've added a new plugin system to Manyfold (coming in v0.146.0). In order to last between container updates, the plugins need to be stored somewhere persistent. I've added a PLUGINS_PATH environment variable which defaults to the app's
pluginsdirectory, but it needs persistent storage mounted at that location, which I've mentioned in our example dockerfile (see manyfold3d/manyfold#6569).Proposed code change
The app will work without persistent storage mounted, and should show a warning on the plugin screen if it's not writable, so nothing should break; however, I imagine you'll want to add how users should set this up in a linuxserver way in your docs. Normally I'd do a PR myself, but I don't want to make assumptions on what you want your users to do.
As an example, in our single-container "solo" image, I've preconfigured the path to
/config/plugins, as there's already an SQLite database at/configand users will already have a volume mounted there that we can use.