Skip to content

AC-18494::Developer document updates for Zend and Symfony cache #190

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.

Sign up for GitHub

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

Merged
meker12 merged 1 commit into from
Sep 30, 2026
Merged

AC-18494::Developer document updates for Zend and Symfony cache #190

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions src/pages/guide/integration/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,36 @@ Leave all the settings that do not start with `db-` and `amqp-` at their default
You can include additional setup options—available to the `setup:install` command—in the test configuration file. A
complete list of options is available in the [Installation Guide](https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/advanced).

#### Run the integration tests against a specific cache backend

By default, the integration tests install with the file-based cache backend. To run the suite against a specific cache
backend instead, add the `cache-backend` option to `install-config-mysql.php`, along with any connection options for
that backend:

```php
return [
// ...
// 'cache-backend' accepts: redis, valkey, symfony_redis, symfony_valkey, zend_l2, symfony_l2
'cache-backend' => 'symfony_valkey',
'cache-backend-valkey-server' => '127.0.0.1',
'cache-backend-valkey-port' => '6379',
'cache-backend-valkey-db' => '0',
];
```

| Value | Description |
| --- | --- |
| `redis` | Legacy Zend-based Redis backend |
| `valkey` | Legacy Zend-based Valkey backend |
| `symfony_redis` | Symfony Cache backend with Redis |
| `symfony_valkey` | Symfony Cache backend with Valkey |
| `zend_l2` | Legacy Zend-based two-level (L1/L2) cache |
| `symfony_l2` | Symfony Cache two-level (L1/L2) cache |

`redis` and `symfony_redis` use the matching `cache-backend-redis-*` options (`cache-backend-redis-server`,
`cache-backend-redis-port`, `cache-backend-redis-db`, and so on) instead of the `cache-backend-valkey-*` options shown
above. All these options default to a local instance at `127.0.0.1:6379`, database `0`, if omitted.

If your project requires custom entries in the `core_config_data` table, such as the introduction of new third-party services
that affect your application on a basic level or configuration for logic that would prevent access if not configured
properly, Commerce provides a file template for this purpose.
Expand Down
Loading