Telemetry environment variables naming and documentation

[rabol]

Hi

by coincident I found the DO_NOT_TRACK, it would be nice if it was a config option and easy to set

[antonmedv]

You're absolutely right. The presence of the DO_NOT_TRACK variable can be confusing, especially since it's commonly used across various tools and platforms to control telemetry and analytics. This ambiguity can lead to unintended behavior if users, developers, or automation scripts unknowingly rely on the same environment variable for different purposes.

To address this, we should consider renaming it to something more specific, like DEPLOYER_TELEMETRY_DISABLED. This name makes its purpose explicitly clear—it's not a generic "do not track" flag but specifically controls telemetry within our deployer. It reduces the risk of conflicts with other software and improves maintainability by ensuring that future developers and users immediately understand its context.

Migrating to a more descriptive variable also aligns with best practices for environment configuration, where variables should be scoped to the system they affect. It prevents accidental overrides in shared environments, simplifies troubleshooting, and ensures that users configuring the deployer know exactly what they are enabling or disabling.

Additionally, we should improve our documentation to highlight this option, explaining its purpose, default behavior, and how to configure it properly. This would not only make the system easier to work with but also encourage more consistent and predictable setups across different environments.