I wish I could be more help but I know nothing at all about AWS 
Howard Miller
Posts made by Howard Miller
Moodle in English -> Installing and upgrading help -> Redis configuration differences -> Redis configuration differences
by Howard Miller -
Yeh - that discussion is wrong.
On the point of configuring both, it's up to you. I would say that using redis for the Cache is a *very* good idea. Using it for sessions is entirely optional. We have that on our production sites but using different Redis servers (in fact different clusters of Redis servers). However, you're right, it works find pointing both at the same server. IIRC, it's not even required to use a different prefix, although it can't hurt.
The cache configuration is a bit weird in that the config gets written to the file muc/config.php within the 'moodledata' file area. I imagine that you could configure it once and then grab a copy of the file to copy to that location. With the large caveat that I have never tried that.
On the point of configuring both, it's up to you. I would say that using redis for the Cache is a *very* good idea. Using it for sessions is entirely optional. We have that on our production sites but using different Redis servers (in fact different clusters of Redis servers). However, you're right, it works find pointing both at the same server. IIRC, it's not even required to use a different prefix, although it can't hurt.
The cache configuration is a bit weird in that the config gets written to the file muc/config.php within the 'moodledata' file area. I imagine that you could configure it once and then grab a copy of the file to copy to that location. With the large caveat that I have never tried that.
Moodle in English -> Installing and upgrading help -> Redis configuration differences -> Redis configuration differences
by Howard Miller -
These are two entirely different things.
The configuration through the admin UI is to configure Moodle's cache (or MUC as Moodle calls it).
The configuration in config.php is to configure using Redis to store Moodle sessions. Nothing to do with the cache.
The configuration through the admin UI is to configure Moodle's cache (or MUC as Moodle calls it).
The configuration in config.php is to configure using Redis to store Moodle sessions. Nothing to do with the cache.
Moodle in English -> Installing and upgrading help -> Upgrading to 5.1? Read this first -> Upgrading to 5.1? Read this first
by Howard Miller -
+1
It's looking like some work is needed. On consistency if nothing else.
It's looking like some work is needed. On consistency if nothing else.
Moodle in English -> Installing and upgrading help -> Changes to Upgrade Moodle 5.1 -> Changes to Upgrade Moodle 5.1
by Howard Miller -
Have to disagree on that.
You can run it as whatever user you like. Debian based distributions of Apache tend to use www-data, Redhat was always 'nobody'. The only "rule" is "not root".
You can run it as whatever user you like. Debian based distributions of Apache tend to use www-data, Redhat was always 'nobody'. The only "rule" is "not root".