Skip to content

Separate core plugins and "user" plugins #12988

@crazy-max

Description

@crazy-max

Hi,

I'm here about an issue concerning plugins path. This comes from matomo-org/docker#89 and matomo-org/docker#97.

Today all plugins (including core ones) are written in /var/www/plugins folder. On a load balanced environment you said to add multi_server_environment=1 in the config and next you said :

it will then not allow the installation of a plugin via the UI (or the plugin would be only installed on one server), or it will not allow config file changes from the UI (as the config file would be updated on one server only)

It's a major issue for me and i think this can be solved with a new feature. We should separate core plugins (included in piwik archive) and user plugins. Nextcloud uses this trick to be able to persist plugins folder on Docker. On Nextcloud you can have this config :

array (
    0 =>
    array (
      'path' => '/var/www/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 =>
    array (
      'path' => '/data/userapps',
      'url' => '/userapps',
      'writable' => true,
    ),
  ),

This way user apps will be written in /data/userapps and plugins are listed from /var/www/apps (core) and /data/userapps (user).

And it's an issue on Docker too (specially on Swarm or k8s). We cannot persist the folder /var/www/plugins because on image update this folder will have core plugins from the previous version of the image.

Metadata

Metadata

Assignees

No one assigned

    Labels

    wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions