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

Redis support #231

Open
3 tasks
Tracked by #229
martin-helmich opened this issue Nov 28, 2022 · 1 comment
Open
3 tasks
Tracked by #229

Redis support #231

martin-helmich opened this issue Nov 28, 2022 · 1 comment

Comments

@martin-helmich
Copy link
Owner

This was requested in #209 (comment).

Adding Redis support would entail the following:

  • The Docker image needs to be built with the PHP Redis extension. Currently, this image uses the official php library images (which may be subject to change, however), so adding the redis extension on top of those should be an easy fix.
  • Depending on the implementation state of Support for automatic installation and configuration via environment variables #230, the TYPO3 configuration could also be adjusted automatically based on the presence of certain Redis-related environment variables.
  • Documentation required.
@SchoolGuy
Copy link

Just for completeness sake I will like the Typo3 Documentation for Redis here: Typo 3 Documentation - Redis

From a standpoint of a drop-in configuration (for example that is generated by a script which then is fed by the ENV variables) this should be fairly easy as we can put this in a dedicated file. I would start with the example provided by the example from the docs and use getenv() to load the actual values. The script would then depending on the value of CACHE_REDIS_ENABLED (allowed values should be 0 or 1) copy the file on container startup to config/system/additional.php. This means that those options cannot be change via the install tool since the file is not touched by Typo 3. However further down the road it will get more complicated to build the additional.php configuration file if we have multiple drop-in sections we want to pass, however I am confident that this is a solvable problem (I already have ideas).

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

No branches or pull requests

2 participants