Add a guide to setup `.env` files for templates that need them.

[Ashrockzzz2003]

Right now templates such as Microsoft OAuth one needs env. After initializing template with qse init, it doesn't work out of the box and needs env vars to be setup. So to templates that have a necessity for env vars, need some guide that gets printed to the console after initializing the template indicating it.

• Propose a way to do this. Console is just one among many. A generic approach is appreciated.
• After the proposal is approved, implement it.

You can reply to this issue with the proposal. If >1 people respond, the best will be chosen!

[PavanCodes05]

Hey @Ashrockzzz2003, I can work on this issue if it is not assingned to anyone yet

My Approach:

1. I Can check if the chosen template has the env file using 'fs'
2. If the template has the ".env" file, we can log the instruction, if not ignore it

If this approach sounds good, kindly give the preferred style for logging the instructions :)
Thank You!

[Ashrockzzz2003]

@PavanCodes05
I get your approach. Do we actually need to read thru file.

We know the templates, we know beforehand whether it needs env or not, how about we just store it in a boolean along with template metadata in configs.js and based on that we log.

About the logging style, try coming up with one. We're open for ideas.

[PavanCodes05]

@Ashrockzzz2003 That's a clever approach, you can assign me I can do that!

[GMHarish285]

@Ashrockzzz2003
Here's my proposal:
Like you said, we will just have a boolean in the const templates in bin/configs.js.
Then, if a template is created which needs .env we will print in CL that this template needs env vars. And maybe provide a short description or just list them in the CL itself. And ask them to refer README.md for detailed info.

And we will also create a README.md which can provide an explanation of the env variables, and how to set them up.
But I guess, this requires the README.md to be created in the template itself.

[PavanCodes05]

Hey @Ashrockzzz2003 ! Good evening,

Enhanced Approach:

1. We can have a boolean flag indicating if a template requiresEnv
2. through that we can indicate the users with "The chosen templated requires env variables to run"
3. the extra thing that we do is, we give them 2-3 seconds to read the terminal, ignoring any I/O to avoid them starting up the application without setting up .env
4. Finally with the indication, we redirect them directly to env file on their default code editor! which makes sure the setup is done before starting up the server!

if this SGTY, I can work on it, Thank you !