Redis sessions, cache & queues

m4v3rick

I have a few question regarding the installation.
How do I know if redis and my set up works?

I don't get any error and my local installation works well. I also used the fake data extension to generate a few bigger fake discussions.

My steps were as follows:

install redis-server
changing the redis conf (another port for security reason, changing maxmemory to 512 and policy to allkeys-lru)
install flarum-redis

changing the extend.php to:

return [
    // Register extenders here to customize your forum!
    new Blomstra\Redis\Extend\Redis([
        'host' => 'localhost',
        'password' => null,
        'port' => XXXXX,
        'database' => 1,
    ])
];

Next steps would be setting up supervisor.

So here are the questions:

Are the steps above correct?
I read in this discussion about different databases for each service. Is this a best practice example?
What is the difference between 2. and 3. (config array) in the info at top? Different passwords and ports?

Edit:
redis-cli -p XXXXX
Responses with a PONG.

luceos

m4v3rick try triggering an email notification to yourself with another user by replying to a discussion you subscribed to 😉

m4v3rick I read in this discussion about different databases for each service. Is this a best practice example?

Not really necessary but if your community has its own dedicated redis instance I do recommend to do it. Otherwise use different databases per community.

m4v3rick What is the difference between 2. and 3. (config array) in the info at top? Different passwords and ports?

Yep or completely different redis instances. Sometimes you want queue and session on a redis instance that persists data on shutdown and cache on an instance that doesn't. 3 allows you to configure different redis instances for each.

m4v3rick

luceos try triggering an email notification to yourself with another user by replying to a discussion you subscribed to 😉

Tried it today on my testing environment with mail driver "log" and "php flarum queue:work". Then I tagged my user and posted. This is the shell result:

[2023-11-14 14:25:28][5z1rlb0sYGqdr7xxzHbZ5eQhjl5ipEN6] Processing: Flarum\Subscriptions\Job\SendReplyNotification
[2023-11-14 14:25:28][5z1rlb0sYGqdr7xxzHbZ5eQhjl5ipEN6] Processed:  Flarum\Subscriptions\Job\SendReplyNotification
[2023-11-14 14:25:28][maFXNkKdzuXY2Eb99h96XD2xQxoKl00f] Processing: Flarum\Mentions\Job\SendMentionsNotificationsJob
[2023-11-14 14:25:28][maFXNkKdzuXY2Eb99h96XD2xQxoKl00f] Processed:  Flarum\Mentions\Job\SendMentionsNotificationsJob
[2023-11-14 14:25:28][JGDPYEiM2BOuYdAO5L0nsnsif57WB7V1] Processing: Flarum\Notification\Job\SendNotificationsJob
[2023-11-14 14:25:28][JGDPYEiM2BOuYdAO5L0nsnsif57WB7V1] Processed:  Flarum\Notification\Job\SendNotificationsJob

So it is working, I guess?

Next step is the supervisor and then a try on production.

luceos

m4v3rick [2023-11-14 14:25:28][JGDPYEiM2BOuYdAO5L0nsnsif57WB7V1] Processed: Flarum\Notification\Job\SendNotificationsJob

Processed implies it work. The queue definitely seems to run without issue so far 👏

m4v3rick

luceos

Since it is my first try with redis and supervisor, would that be a reasonable conf for supervisor?

[program:flarumredis-worker]
command=/var/www/flarum php flarum queue:work
autostart=true
autorestart=true
stderr_logfile=/var/log/redis_flarum.err.log
stdout_logfile=/var/log/redis_flarum.out.log

Or anything else to consider?

ernestdefoe

m4v3rick

[program:redis] command=/usr/bin/php flarum queue:work directory=/var/www/path to flarum numprocs=1 autostart=true autorestart=true user=www-data stdout_logfile=/var/www/path to flarum/storage/logs/redis.log stderr_logfile=/var/www/path to flarum/storage/logs/redis-error.log

This is what I have in mine and it's working fine. Just change the path to flarum to your path. Save it and restart supervisor. You may also need to change the user but for my setup www-data works fine. It took some trial and error to figure this out and get it working but I looked at the Realtime config file and info someone else posted above and figured out something that worked. Hope this helps you.

m4v3rick

luceos

With Supervisor.

Edit: I found the error. My conf file didn't save but there was no error. Now it is just a few seconds. And seems to work fine.

But

ernestdefoe command=/usr/bin/php flarum queue:work
directory=/var/www/path to flarum

That helped a lot. Thanks @ernestdefoe .

Just found out that this

m4v3rick command=/var/www/flarum php flarum queue:work

doesn't work at all.

m4v3rick

ernestdefoe

Thanks.
My configuration seems to work on my test system.
I just wonder about the notification time now.

If I open the local flarum instance in two different browser with two different users logged in for each browser and I tag the other user, I see that there is a new post after refreshing manually the browser but no notification.
The notification is shown one minute after the post is done. I know it is queued and the behaviour seems correct but is there a possibility to change the time for the worker to work off the queue? Like 30sec?

Oh and btw. this is shown in the backend:
Queue Driver: redis
Session Driver: redis

So it seems to be configured correctly.

m4v3rick

Why do you use this?

ernestdefoe numprocs=1

And that I don't need.

user=www-data

luceos

m4v3rick Like 30sec?

Go into your admin area settings for realtime, underneath "Interval to automatically push new discussion activity" set it to 30. You can also disable that completely and push all updates to the client immediately by disabling the toggle above that input field.

Or are you using pusher?

ernestdefoe

m4v3rick I’m glad it seems to be working correctly for you. I had a time trying to get Redis and Realtime running correctly on my VPS but after a ton of trail and error and wiping the VPS and starting over again multiple times I finally got it working. I had one issue where when installing extensions after having so many installed it would “crash” my site come to find out I didn’t have enough memory allocated to PHP so I bumped that up and no more issues.

m4v3rick

ernestdefoe I’m glad it seems to be working correctly for you.

Thanks but it is just test environment yet and only redis queue.

luceos Go into your admin area settings for realtime, underneath "Interval to automatically push new discussion activity" set it to 30. You can also disable that completely and push all updates to the client immediately by disabling the toggle above that input field.

Or are you using pusher?

I just installed redis yet. No pusher no realtime.
There is no admin panel for redis?!

luceos

ernestdefoe the harder the lesson, the better you remember it 😉

ernestdefoe

luceos this is true. I bet I could set both of them up now with my eyes closed as I’ve had to type it all out so much. Now just to get some activity and members on my site just to make sure everything works correctly. Now if I could just figure out how to get Elasticsearch set up. That thing has given me more of a headache than anything.

luceos

ernestdefoe elastic is really overkill unless you have a massive community.

ernestdefoe

luceos trying to prepare for the future. I know right now it is overkill.

luceos

m4v3rick I misread your post I think. So all tasks in the queue are delayed by 60 seconds? How did you set up the queue worker command, using a cronjob or as a daemon?

m4v3rick

I tried php flarum queue:listen.

Should that show everything inside the queue?

ernestdefoe

@m4v3rick I was just using what I saw in other config files. Not sure why anything is in there I'm an idiot when it comes to this stuff but and I am doing my best to figure it out.

m4v3rick

ernestdefoe I am doing my best to figure it out.

If it works, then you are doing everything right. 🙂

I just installed the redis queue on production. Let's see how that goes.

Still want to seperate a discussion into several parts to speed up the loading time but don't know how.

« Previous Page