fof/redis >=1.1 introduces a `settings` service that replaces
SettingsRepositoryInterface with a Redis-backed caching layer.
Enabling it here creates a circular dependency: this extension reads
settings to decide which Redis services to enable, but with the
settings cache active those reads require Redis to already be wired.
Always disable the `settings` service when delegating to fof/redis.
Also fixes a cast-precedence bug in the database env var helpers
where `(int) getenv(...) ? getenv(...) : N` applied the cast to the
ternary condition rather than the result, causing REDIS_DATABASE_*=0
to return the default instead of 0.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore: migrate to fof/redis, repo maintenance
* chore: newline
* chore: use new fof horizon initializer
* chore: revert initializer change
Only changed for 2.x ..
* chore: remove unused secrets
Shouldn't have been added in the first place
---------
Co-authored-by: Davide Iadeluca <146922689+DavideIadeluca@users.noreply.github.com>
Co-authored-by: Davide Iadeluca <davide.iadeluca@glowingblue.com>
