Skip to content
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

Clarified on the usage of Redis and PHP 7.0+ is required now #1140

Merged
merged 1 commit into from
Jan 15, 2019

Conversation

MorrisJobke
Copy link
Member

No description provided.

Signed-off-by: Morris Jobke <hey@morrisjobke.de>
@MorrisJobke
Copy link
Member Author

/backport to stable15

@@ -99,7 +104,7 @@ If you want to connect to Redis configured to listen on an Unix socket (which is
recommended if Redis is running on the same system as Nextcloud) use this example
``config.php`` configuration::

'memcache.local' => '\OC\Memcache\Redis',
'memcache.local' => '\OC\Memcache\APCu',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you can have both local memcache and distributed?
How the data distribution is done?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's by requirement: so if the data is fine to be stored locally only then this is used if it needs to be instance wide cached in the same way then the distributed one is used.

By default the distributed one is requested. Local one is typically used for PHP objects and stuff that is highly specific to that system and not the instance at a whole.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! Thanks for the clarification !

@backportbot-nextcloud
Copy link

backport to stable15 in #1151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants