@maishivamhoo123 You submitted language and configuration files that should not have been submitted.

Sorry sir for the confusion. I won’t repeat this again.
Just to confirm, I should add only the following files:

main.go

.env.example

.gitignore

README.md

go.mod
@LinkinStars Sir Please let me know if this is correct.
Thank you for your guidance, sir.

Sorry sir for the confusion. I won’t repeat this again. Just to confirm, I should add only the following files:

main.go

.env.example

.gitignore

README.md

go.mod @LinkinStars Sir Please let me know if this is correct. Thank you for your guidance, sir.

@maishivamhoo123 I think we can skip modifying README.md. We can add this instructions to https://answer.apache.org/docs/env

Understood, @LinkinStars sir.
So instead of modifying README.md, I should add the relevant instructions to the documentation at https://answer.apache.org/docs/env
.
Thank you for your guidance.

@LinkinStars Sir,
I hope this PR looks good now. If there are any remaining issues or further improvements needed, please let me know—I’ll be happy to address them.

Thank you for your guidance .

@maishivamhoo123 I verified this feature, and it has issues. It fails to correctly read environment variables via .env. This is clearly because the current environment variables are not read within the function itself, but rather within the var scope.

Thank you @LinkinStars Sir for your review. You are right, package-level variables are defined before init() runs.

I have fixed this by defining the variables globally and assigning their values inside the init() function. I ran the test and it is running fine: