Option to generate your .env file during ./init.sh

[gingerchew]

Feature request

Summary

After running the ./init.sh script for the first time, I noticed that there was a check for a .env file, but no instructions on the documentation about it. I think adding a prompt to generate one in the terminal, similar to npm init and other commands.

Why is it needed?

Makes it a clearer what is going on. Maintains user control.

Suggested solution(s)

I have a solution, added to the original if;else 🔗 here
You can see I had prompts for the URL and alias fields. This seemed redundant since the example file suggested they would all be derived from the project name.

Related issue(s)/PR(s)

I haven't made a PR yet, but if you review the above code I can certainly pull one together. Unnecessary comments and what not.

Example of skipping through but selecting a MODx version