I just want to share with you a small point of view on the Qovery Template.
It concern especially the .env file. As you may know it’ not really cool to have a .env file expose on your Git repository & in your commit/push.
When you use a Qovery Template it push to your repository the .env file in order to inject some default environment variable to Qovery. The bad things is that every time you’ll use a Qovery Template, you’ll have to remove from your git this .env file and then push the modification in order to clean your Git.
You may tell me that it’s not that bad and that it’s just another step, but if you don’t know about this you won’t do it and you’ll - like I did the first time I used a Qovery template - expose your private env variables.
For that it would be great if there was a way to put a config file for each template that tells Qovery what env variables to inject by default (like the .env) but it would not be pushed to the user’s git repository created by the template
I hope this will help