Redis sessions, cache & queues

HHari · Jun 25, 2021

is this supported for v1.0.3? (flarum latest version)

[0]:ask$ composer require glowingblue/redis-setup
Using version ^1.0 for glowingblue/redis-setup
./composer.json has been updated
Running composer update glowingblue/redis-setup
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
                                                                                                                                                                        
  Problem 1                                                                                                                                                             
    - glowingblue/redis-setup 1.0.0 requires blomstra/flarum-redis ^0.4 -> found blomstra/flarum-redis[0.4.0-beta, 0.4.0-beta.2, 0.4.0-beta.3] but it does not match you
r minimum-stability.                                                                                                                                                    
    - glowingblue/redis-setup 1.0.1 requires blomstra/flarum-redis ^0.4.0@beta -> found blomstra/flarum-redis[0.4.0-beta, 0.4.0-beta.2, 0.4.0-beta.3] but it does not ma
tch your minimum-stability.                                                                                                                                             
    - Root composer.json requires glowingblue/redis-setup ^1.0 -> satisfiable by glowingblue/redis-setup[1.0.0, 1.0.1].                                                 
                                                                                                                                                                        
                                                                                                                                                                        
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
[0]:ask$ composer require blomstra/flarum-redis:*
./composer.json has been updated
Running composer update blomstra/flarum-redis
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
                                                                                                                                                                        
  Problem 1                                                                                                                                                             
    - blomstra/flarum-redis 0.1.0 requires flarum/core ^0.1.0-beta.10 -> found flarum/core[v0.1.0-beta.10, ..., v0.1.0-beta.16] but it does not match your minimum-stabi
lity.                                                                                                                                                                   
    - blomstra/flarum-redis[0.2.0, ..., 0.2.3] require flarum/core 0.1.0-beta.15 -> found flarum/core[v0.1.0-beta.15] but it does not match your minimum-stability.     
    - Root composer.json requires blomstra/flarum-redis * -> satisfiable by blomstra/flarum-redis[0.1.0, ..., 0.2.3].                                                   
                                                                                                                                                                        
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.                              
                                                                                                                                                                        
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

luceos · Jun 25, 2021

Hari that's caused by the fact that this package is only tagged as a beta stability.

I just tagged 0.4.0 which is 0.4.0-beta.3 but stable. Feel free to give this another try in a couple of minutes (when composer/packagist caught up).

IanM · Jun 25, 2021

Hari I've just published 1.0.2 of glowingblue/redis-setup, please update to this version, and your problem should be resolved

1Dot · Jun 30, 2021

Can anyone tell me is sessions here means realtime updates like pusher??

1Dot · Jun 30, 2021

luceos null

Here I have to write database password??

luceos How do I configure a redis socket?

Unable to understand where to paste the below code?

Can anyone give me detailed steps in order to install, enable and use this,? as maybe it also requires installing redis in linux?

luceos · Jun 30, 2021

1Dot no, in fact sessions means once you are logged in so that the server understands who you are.

1Dot please understand this is an advanced utility. You have to be able to manage your server. If you don't understand the instructions provided it's best to get professional help or alternatively rely on the glowingblue redis setup extension. In both cases basic understanding of installing and configuring services like redis are recommended.

sanwhere · Jul 10, 2021

I can't see the extension in admin panel. is this normal?

HHari · Jul 10, 2021

sanwhere this is not a extension , read first post (documentation) to configure correctly

luceos If you don't understand the instructions provided it's best to get professional help or alternatively rely on the glowingblue redis setup extension. In both cases basic understanding of installing and configuring services like redis are recommended.

sanwhere · Jul 10, 2021

Hari thanks, I figured it out. it is working now.

HHari · Jul 10, 2021

sanwhere i have installed this but did not setup

we just need to add to these lines to extend.php right?

return [
    new Blomstra\Redis\Extend\Redis([
        'host' => '127.0.0.1',
        'password' => null,
        'port' => 6379,
        'database' => 1,
    ])
];

luceos · Jul 10, 2021

Hari use different databases please. See the instructions.

HHari · Jul 11, 2021

luceos i have added this in extend.php file

return [
    (new Blomstra\Redis\Extend\Redis([
        'host' => '127.0.0.1',
        'password' => null,
        'port' => 6379,
        'database' => 1,
    ]))
    ->useDatabaseWith('cache', 1)
    ->useDatabaseWith('queue', 2)
    ->useDatabaseWith('session', 3)
];

if i run this command php flarum queue:work

i am getting this result

[2021-07-11 07:56:00][qByowZ3FOKSbh28b6wNoaYkztHZE9hBK] Processing: Flarum\Notification\Job\SendNotificationsJob
[2021-07-11 07:56:00][qByowZ3FOKSbh28b6wNoaYkztHZE9hBK] Processed: Flarum\Notification\Job\SendNotificationsJob

does this mean its working?

luceos · Jul 11, 2021

Hari yes it is. Now you need to set the worker up as a daemon, using supervisor or systemd.

HHari · Jul 11, 2021

luceos sorry, i am not getting this step

so i need to install supervisor its an extension from larvel (server level) and need to configure it right?

https://laravel.com/docs/6.x/queues#supervisor-configuration

Edit: i don't have access, cloudways limit certain commands. its a long process to explain them regarding this. i will wait for GB setup

luceos · Jul 11, 2021

Hari gb setup won't solve this. This step is required to have the queue process jobs in the background, unattended. To get this done it needs to run as a daemon, continuously and be restarted on failure. If you don't take care of this step, pending jobs will pile up without being processed.

HHari · Jul 11, 2021

luceos I want to show cache pages to logged out users and spiders.

Can I just go with redis cache without the quee and sessions? Will that requires daemon setup?

luceos · Jul 11, 2021

Hari sessions and cache work perfectly fine without the queue. Make sure to use disable('queue') in your extend.php:

return [
    (new Blomstra\Redis\Extend\Redis([
        'host' => '127.0.0.1',
        'password' => null,
        'port' => 6379,
        'database' => 1,
    ]))
    ->useDatabaseWith('cache', 1)
    ->useDatabaseWith('session', 3)
    ->disable('queue')
];

rafaucau · Jul 11, 2021

Hari i don't have access, cloudways limit certain commands. its a long process to explain them regarding this. i will wait for GB setup

If you don't have full access on the server because you have shared hosting, for example, then you can still use Redis Queue.
What I did was to set up a cron for such a script:

#set -x

queue=`ps -aux | grep "flarum queue:work" | grep -v grep`
if [[ -z $queue ]]; then
while true :
	do
		[[ -z $queue ]] && { php flarum queue:work; }
	done
else
exit 0
fi

When a process fails for some reason, cron will start it again.

HHari · Jul 11, 2021

luceos after updating this website is showing 500 error

rafaucau i do have access but its hard for me to setup daemon

luceos · Jul 11, 2021

Hari any errors in storage/logs?