DX-686/missing-envs

[Isengo1989]

Everything past COMPOSER_PLUGIN_LOADER was added.

[Copilot]

Pull Request Overview

This PR adds missing environment variable documentation to the Shopware configuration guide. The primary purpose is to expand the environment variables reference table with 18 previously undocumented configuration options covering Redis, Elasticsearch/OpenSearch, administration interface, and other system settings.

Key changes:

• Aligned table column separators for consistent formatting
• Added 18 new environment variables with descriptions and default values covering Redis, service registry, administration paths, Fastly CDN, Elasticsearch/OpenSearch configuration, and system feature toggles

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] The description 'Redis connection URL for caching and sessions' should include an example format (e.g., redis://localhost:6379) to help users understand the expected URL structure.

Suggested change

	| `REDIS_URL` | (empty) | Redis connection URL for caching and sessions |
	| `REDIS_URL` | (empty) | Redis connection URL for caching and sessions (example: `redis://localhost:6379`) |

[Copilot]

[nitpick] Consider adding a note that this API key should be kept secure and not committed to version control, similar to how APP_SECRET is documented.

Suggested change

	| `FASTLY_API_KEY` | (empty) | API key for Fastly CDN integration |
	| `FASTLY_API_KEY` | (empty) | API key for Fastly CDN integration. **Keep this value secure and do not commit it to version control.** |

[Copilot]

[nitpick] The description should clarify the accepted boolean values (e.g., '1' for enabled, '0' for disabled) to match the pattern used for other boolean environment variables in the table.

Suggested change

	| `SHOPWARE_ES_THROW_EXCEPTION` | `1` | Whether to throw exceptions on Elasticsearch errors |
	| `SHOPWARE_ES_THROW_EXCEPTION` | `1` | Whether to throw exceptions on Elasticsearch errors (`1` to enable, `0` to disable) |

[mitelg]

@Gaitholabi @AydinHassan is that correct?

[AydinHassan]

Yeah but honestly I'm not sure if we should document this - it's not really something that should be customised and is mostly used for us to switch to the testing registry. wdyt @keulinho ?

[Isengo1989]

Yup, this was found in the devenv.nix

env.SERVICE_REGISTRY_URL = lib.mkDefault "https://registry.staging-services.shopware.io";

If there is NO use-case-scenario for customers, we can ignore it.

[AydinHassan]

We might in the future document how to use it with the testing environment or provide a different customer facing one. But at this point the API is not even public so it would be pretty hard for someone to build a custom implementation and it might cause issues putting a random different url in there.

[mitelg]

@jleifeld would you mind checking admin related env variables?

[mitelg]

could not find this one in the code 🤔

[aragon999]

The SERVICE_REGISTRY_URL and SHOPWARE_ADMINISTRATION_PATH_NAME are defined directly in the container. The other ones I am also not aware of.

[mitelg]

@shopware/product-cc-inventory would you mind checking those ES variables?

[vienthuong]

LGTM, only small suggestion is SHOPWARE_ES_ENABLED, SHOPWARE_ES_INDEXING_ENABLED, OPENSEARCH_URL should be re-order with other ES variables below, or we can think of moving it as a separated table (with 13 ES variables that they can ignore or refer to whether they use ES or not)

[Isengo1989]

@vienthuong had the same thought - ES is pretty specific/groupable, and most probably are not using it. Will do.

[mitelg]

deprecated