Redis sessions, cache & queues

tony321

why not store session?

luceos

tony321 that could be added without too much issue. I guess it makes sense too, just didn't run into the need to add it yet.

userb

does this support key prefix like memcache to use the same database or you have to select different database to prevent collision?

luceos

userb you should use different databases. But these are auto created on their first use. The default database limit is 16. So pick a number up to that.

matteocontrini

Hi. Could this be considered beta.14 compatible? At a first glance it should, but it's still targeting beta10 🙂

luceos

I'd like to point out that bokt/flarum-redis is not compatible with beta 14 or 14.1. We will skip this version and offer compatibility with beta 15 which is expected within a few weeks.

The reason for this is a pull request which makes the necessary implementation much easier: flarum/core2481.

clarkwinkelmann

@luceos it seems like your version constraints prevent installation on patch releases (ex. -beta.15.1) in case of a Flarum security release.

Also since it wasn't announced here, I can report that the beta 15 update has indeed been tagged.

mekici

luceos I guess php flarum cache:clear command does not work while the Redis plugin is active. What should be done if the cache needs to be cleared in this situation?

luceos

mekici it actually does work. What issue do you have exactly?

mekici

luceos today i uninstalled bokt / flarum-redis (v2.0) plugin and installed blomstra / flarum-redis plugin. While bokt / flarum-redis latest) plugin was installed, php flarum cache: clear command was running. In blomstra / flarum-redis plugin, it gives a warning like in the picture.

Flarum Beta 15,
Redis: v4.x.x

luceos

mekici rollback to 2.0 for the time being. This seems a bug. Can you create an issue on the repository with you redis version and the screenshot and trace? I will look at this as soon as possible.

mekici

luceos When v0.2.0 returns, php flarum cache: clear is running. I am creating an issue

blomstra/flarum-redis8

luceos

Tagged 0.2.3 which flushes the textformatter cache when clearing.

Still need to look at your issue @mekici, will answer on GH.

PS We moved this to Blomstra, please update your composer file.

DursunCan

luceos How can I always run the php flarum queue:work command?

mekici

DursunCan https://flarumtr.com/blog/2293-flarumda-supervisor-kullanimi

luceos

The recommendation is to use supervisor: https://laravel.com/docs/6.x/queues#supervisor-configuration

matteocontrini

On distributions with systemd (e.g. Ubuntu), it's also possible to create a system service without installing anything. Here's an example:

/etc/systemd/system/flarum-queue.service

[Unit]
Description=flarum-queue
After=network.target
StartLimitIntervalSec=0

[Service]
Type=simple
User=deploy
WorkingDirectory=/var/www/flarum
ExecStart=/usr/bin/php flarum queue:work
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Then, once:

sudo systemctl start flarum-queue
sudo systemctl enable flarum-queue

xasharma

matteocontrini I have done this all with all step many time but it stops giving notification after 3-4 hours.

@HD3D Please guide

matteocontrini

Is Discuss using this extension? 🙂

luceos

matteocontrini yes it is. We're using Laravel Forge to set up the daemon though.

In my opinion there are three stages of running queues:

default - in process - for smallish communities; up to 10 notifications to be send per trigger/event
this extension for medium communities, an occasional job failing is no issue
the horizon extension (still needs some work to be made compatible with the latest core version if I remember correctly) for larger communities that also need insight when jobs fail

matteocontrini

luceos thanks 😃

Looking at the Laravel documentation, is the failed_jobs table something that can be used with this extension, in order to still have some manual control on failed jobs?

« Previous Page Next Page »