consider varlock for env/secrets loading and validation

[theoephraim]

I noticed you have a .env.example and a .env.schema.json and a custom validation script, as well as additional code to scan for git leaks.

You could replace a lot of this using varlock. This gives you a single .env.schema which replaces your .env.example with a .env.schema that is safe to commit. There are 15 different plugins to fetch from various locations (1password, infisical, vault, aws, etc), or users can still put items in a gitignored .env file. It has value based git scanning, log redaction, leak detection, and tons of other nice features.

Happy to help you get it set up if there is interest.

[gabsprogrammer]

Thank you for the suggestion, I sent it to @Lightheartdevs for review.

[Kuldeep-Singh-Naruka]

I've reviewed the current .env.schema.json and validation scripts — I'd like to explore whether varlock fits here. I'll start by mapping the current validation logic and post a comparison.