Question Private redis instances per subscriber

[Brightside]

Hello. There are a lot of caching extensions, but I'd say Redis is a standard now for majority of CMS, however there is no simple way to provide Redis service for subscribers. Shared Redis isn't an option because it's just insecure and limited by 16 bases per server.

Redis using Docker isn't option too.

cPanel Redis® Plugin - there is a plugin for cpanel. It would great to have something like that for Plesk out of the box. Like Redis on request or as paid option.

 

[virtubox]

Hello. There are a lot of caching extensions, but I'd say Redis is a standard now for majority of CMS, however there is no simple way to provide Redis service for subscribers. Shared Redis isn't an option because it's just insecure and limited by 16 bases per server.

Redis using Docker isn't option too.

cPanel Redis® Plugin - there is a plugin for cpanel. It would great to have something like that for Plesk out of the box. Like Redis on request or as paid option.

In /etc/redis/redis.conf, you can edit the database limit and use more than 16 databases by redis instance.
Otherwise, with the compilation method explained in resources, you can run several redis instance on the same host by using another port and service name for each redis instance.

 

[Brightside]

In /etc/redis/redis.conf, you can edit the database limit and use more than 16 databases by redis instance.
Otherwise, with the compilation method explained in resources, you can run several redis instance on the same host by using another port and service name for each redis instance.

As I said shared Redis isn't an option. It's just not secure, because there is no ACL. Any redis user will be able view and edit any redis database. Compilation is great, but it is a pain. It needs to be automated somehow, probably centralized, probably redis instances should be run on another server.

I'd say Redis becomes an essential service such as mail (Imagine that you need to compile postfix for each user )

 

[bulent]

Why docker is not an option?

 

[Brightside]

Why docker is not an option?

There are a lot of reasons. Docker does not provide desired automation (you still need to run containers manually, you need to provide auth password for subscriber and store it somewhere), but brings risks. Half of Docker storage drivers are buggy and slow, docker isn't working correctly with modern firewalls like firewalld/ufw. Plesk in this case is additional layer of middleware which I wouldn't like to use.

 

[IgorG]

Thank you for idea. We have submitted it as internal feature request PPM-2410.