New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New FAQs to document how to use Redis for sessions and cache #7767
Comments
Maybe we could even write a blog post on how to use Redis when using Piwik in a load balanced environment and also include QueuedTracking plugin for handling peaks etc. I will create an issue for this. |
Maybe something like this? @mattab How to configure Redis as a shared cache in a load balanced environmentBy default Piwik caches data in the local filesystem of each server. If your Piwik environment consists of multiple servers a common problem is that caches are only invalidated on one server instead of all servers. To workaround this we recommend to use a shared cache for all of your servers. You can do this by installing and configuring Redis. To use Redis as a cache follow these steps:
How to configure Redis for session handling in a load balanced environmentBy default Piwik uses the filesystem as a session handler. If your Piwik environment consists of multiple servers a common problem is that multiple sessions are created per user meaning a user might have to log in multiple times and a log out might actually log out a user only on one server. To workaround this there are two options:
To use Redis as a session handler follow these steps:
See Redis Session Handler for more documentation.
|
assigning to @mattab for now to put it into FAQ in case it is ok |
Text is very clear, both FAQs have been published: Nice new resource for admin who want to re-use the power of Redis! |
“session.save_path = tcp://127.0.0.1:6379?database=10”invalid ,Excuse me where is the problem? |
The goal of this issue is to document in the FAQs
follows up #6800
The text was updated successfully, but these errors were encountered: