Horizon, scalable redis queues and dashboard

[deleted]

luceos I understand a little but all I need to do in order to increase functionality is

composer require blomstra/flarum-redis:*
composer require blomstra/horizon:"*@beta"

OR Anything else also?
If I am correct only like the post!

luceos

[deleted] you don't need to download/install blomstra/flarum-redis, this extension takes care of that. But understand that you can only use blomstra/horizon and blomstra/flarum-redis if:

you have a running and accessible redis server available and you know how to reach it
you are able to set up the queue worker (commands differ for redis vs horizon) so that they are running permanently

If you don't know what I'm talking about, it's better to stay away from these two packages.

[deleted]

luceos I am unable to understand what all is this I have maximum traffic of 15 - 20 k is it any need for it as it looks something really hard.

luceos

[deleted] you will notice automatically when you need to start using queues, posts you make will take longer and longer the more people are subscribed to updates. The "Following" feature from flarum/subscriptions, the fof/follow-tags and ian/follow-users extensions increase the number of notifications that have to be send.

[deleted]

luceos Hmm ( Thanks for Replying )
Is Discuss.Flarum.org using this?

luceos

[deleted] discuss does not use horizon, it uses the simpler redis queues: https://discuss.flarum.org/d/21873-redis-sessions-cache-queues

I made a Flarum extension out of Laravel Horizon for Bokt.nl, my employer. For his ongoing migration from phpBB to Flarum with over 100 million posts, we are keeping both in sync with each other; that all happens in the Queue. So it became apparent that having a scalable queue solution and some insights into failing queue jobs would be crucial.

Darkle

luceos Quite interesting, do you think it would work with ReCache?

luceos

Darkle recache also uses redis but instantiates it separately. It should not cause any conflicts.

Debaucus the reason it isn't default is because redis is not available on shared hosting environments. It also requires technical knowledge because you need to set up the runner to run continuously.

Debaucus

luceos Reading the little explanation of Redis, may I ask what the disadvantages are?

I am really asking, why isn't this the default? You explain a use case where this improves but what are the drawbacks?

Littlegolden

looks like the url is hard coded, if I change admin page's url to admin_xxxx in config.php ,horizon will still use admin as the url, this cause the assets load error of 404.

luceos

Littlegolden could be, understand that the URL is protected using Flarum's authentication anyhow. Only admins can access it.

mys

😐

luceos

mys hm looks like the RedisQueue isn't instantiated..

Just tagged 0.2.1, try now.

mys

luceos okay

IanM

0.3.0

fix: Horizon dashboard was not accessible on Flarum subfolder installations

Updating

composer require blomstra/horizon:"*"

IanM

0.3.1

Support Flarum assets being offloaded to a remote filesystem (S3, ect)

0.3.2

Automatically restart the queue after clearing cache, extension enable/disable, settings change (Supports Flarum 1.2.x - 1.4.x only, ¹.5 will support this naitively)

Updating

composer require blomstra/horizon:"*"
php flarum cache:clear

Note: You may need to disable & re-enable the extension after upgrading if you experience any missing css on the Horizon dashboard

luceos

0.3.3

Removed the queue restarting logic, this has been moved into core.

Updating:

composer require blomstra/horizon:"*"
php flarum cache:clear

IanM

0.4.1

feat: add admin dashboard overview blomstra/flarum-ext-horizon17
fix: css no longer targets the Horizon logo correctly on the full Horizon dashboard
fix: some Horizon information pages unaccessible
fix: dark mode support for Horizon dashboard

luceos

0.4.2

feat: improved dashboard stats, allow trim config by @IanM in blomstra/flarum-ext-horizon18

Full Changelog: blomstra/flarum-ext-horizon0.4.1 → 0.4.2