Support for LScache #1358

New Issue

OVERLORD · 2026-02-05T00:41:29+03:00

OVERLORD commented

2026-02-05 00:41:29 +03:00

Originally created by @vlude on GitHub (Sep 12, 2019).

Describe the feature you'd like
Is it possible to integrate support for Litespeed Cache in Bookstack?

Describe the benefits this feature would bring to BookStack users
A lot of hosting environments use Litespeed as webserver, as it's a a drop-in replacement for apache.

Additional context
They have a laravel plugin, which seems to function as a some sort of cache driver. However, my knowledge of laravel is not really great.

Originally created by @vlude on GitHub (Sep 12, 2019). **Describe the feature you'd like** Is it possible to integrate support for Litespeed Cache in Bookstack? **Describe the benefits this feature would bring to BookStack users** A lot of hosting environments use Litespeed as webserver, as it's a a drop-in replacement for apache. **Additional context** They have a [laravel plugin](https://github.com/litespeedtech/lscache-laravel), which seems to function as a some sort of cache driver. However, my knowledge of laravel is not really great.

OVERLORD closed this issue

2026-02-05 00:41:31 +03:00

OVERLORD commented

2026-02-05 00:41:34 +03:00

@ssddanbrown commented on GitHub (Sep 13, 2019):

Thanks for your request @vlude.

The linked plugin requires specific logic to be added to the codebase to support, which I don't think will be worth it since Litespeed will still be a relatively small portion of users then it'll again be only a small portion of those users that would then care or have a need for this level of caching. Additionally, the cache rules would really depend on individual usage so would have to be made configurable which will be extra hassle to implement and maintain.

For route/page/server caching I'd prefer users do this via server configuration, since it means we can focus on the app instead of the environments it sits within.

If you're having any specific performance problems that have lead you to look at caching, please feel free to raise those.

@ssddanbrown commented on GitHub (Sep 13, 2019): Thanks for your request @vlude. The linked plugin requires specific logic to be added to the codebase to support, which I don't think will be worth it since Litespeed will still be a relatively small portion of users then it'll again be only a small portion of those users that would then care or have a need for this level of caching. Additionally, the cache rules would really depend on individual usage so would have to be made configurable which will be extra hassle to implement and maintain. For route/page/server caching I'd prefer users do this via server configuration, since it means we can focus on the app instead of the environments it sits within. If you're having any specific performance problems that have lead you to look at caching, please feel free to raise those.

OVERLORD commented

2026-02-05 00:41:39 +03:00

@vlude commented on GitHub (Sep 13, 2019):

Thank for the consideration. I understand that the benefits for a small amount of users offsets the extra work that is need in maintaining the code.

@vlude commented on GitHub (Sep 13, 2019): Thank for the consideration. I understand that the benefits for a small amount of users offsets the extra work that is need in maintaining the code.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1358