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.
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.
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.
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, 1.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
tohsakarat It sounds that "retry"for failed job does not work The post request of https://xxx.club/admin/horizon/api/jobs/retry/xxxx returns status code 400
luceos 0.4.3 fix: Max memory always displays auto by @IanM in blomstra/flarum-ext-horizon19 feat: display memory eviction policy in redis admin widget by @IanM in blomstra/flarum-ext-horizon20 Full Changelog: blomstra/flarum-ext-horizon0.4.2 → 0.4.3 tohsakarat can you push this into an issue if this still exists: blomstra/flarum-ext-horizonissues ? Thanks.
tohsakarat luceos after using litespeed, I can not see failed jobs/completed jobs in horizon dashboard, but only err message in the log file. response header： Alt-Svc: h3=":443"; ma=86400 Cache-Control: max-age=0, no-store Content-Encoding: gzip Content-Length: 41 Content-Type: application/json Date: Fri, 24 May 2024 12:00:14 GMT Referrer-Policy: same-origin Server: LiteSpeed Vary: Accept-Encoding Via: 1.1 14bcb6b1490628f7642320bd494c55c8.cloudfront.net (CloudFront) X-Amz-Cf-Id: K3te1wmvBPSvotvd-nj4LmOXozRp0w6qZ2hBnpiS2FTcfX0lKtqLuA== X-Amz-Cf-Pop: LAX50-C4 X-Cache: Miss from cloudfront X-Content-Type-Options: nosniff X-Csrf-Token: XlTuNdTgKoXT6PIQk9aIupTFk1mszaqXGaYVmw0J X-Litespeed-Vary: cookie=flarum_lscache_vary,cookie=flarum_remember,cookie=locale X-Turbo-Charged-By: LiteSpeed
