EnvSync από jaytank_dev

Rewriting the same environment variables by hand between a .env file, a Docker Compose environment: block, a GitHub Actions env: block, and a Kubernetes ConfigMap data: block currently means finding a separate website. EnvSync does it in a popup: paste in one format, pick the source and target, get a ready-to-copy result.

--> Scope (v1):
Docker Compose output is list-form only (- KEY=value); Kubernetes ConfigMap covers just the data: block's key-value pairs, not the full manifest wrapper - both are documented, deliberate v1 simplifications.

--> What it doesn't do:
- Reads or interacts with zero web pages - it's a pure client-side text tool operating only on what you paste into its own popup
- Makes zero network requests, requests zero permissions