@DoctorG_1, look if Andi gave a valid answer

Based on the context, there are several approaches to handle environment-specific rules that need different variable settings:

1. Use a file to point to the correct environment:
- Create a `.venv` or similar file that contains the path to the environment-specific configuration[^1]
- Tools and IDEs can read this file to determine which environment to use
- Avoids having to manually set/unset environment variables

2. Use environment-specific config files:
- Create separate config files for each environment (dev/test/prod)[^1]
- Name them distinctly (e.g. dev.cfg, test.cfg, prod.cfg)
- Point to the correct one using a single environment variable

3. Use a script to manage environment switching:
```bash
# Example script
if [ "$ENV" = "dev" ]; then
export CONFIG_PATH=/path/to/dev/config
elif [ "$ENV" = "test" ]; then
export CONFIG_PATH=/path/to/test/config
fi
```

The key is to set up the configuration once and have tools reference it, rather than managing multiple environment variables directly. This provides a single source of truth for environment-specific settings.

[^1]: [Using different redirects across different contexts/environments](https://answers.netlify.com/t/using-different-redirects-across-different-contexts-environments/2524)