Theres are plenty of good reasons to have a service in a template deploy from a GitHub repository, for example, pocketbase does not publish docker images.

but that means a repository is cloned into the user's account every time they deploy, they don't need that repo in their account, so its just left dangling in their account, this becomes worse if a single user were to deploy that template multiple times, multiple useless cloned repositories.

Instead, I would like a way for the template creator to turn off this repository cloning behavior per template service, and if the user decides they want to clone at a later date they would have that option in the services settings.

A big thing that would be useful for the users deploying templates, is if they were somehow shown the overview when deploying templates from the dashboard, I have a few templates that have some commonly asked questions answered in the overview, but since the users were never shown the overview they came to #Help instead, I showed them the overview and that answered their questions, this has happened a hand full of times, that means even more people where left with questions but never bothered to open a thread.

Update

We now automatically create forum threads when a template is published. Y'all should see them coming through within the templates section on this website.

We also link to the thread on the template details page so users can find it organically and ask questions + share feedback.

1. there should be a 'view details' or expansion arrow that shows exactly what values were chosen in the 'create template' ui. it should match 1:1
   or a 'clone this template' button that prepopulates the create template ui with the values

2. rating and comments system

3. require a github repo for the template

4. link to the github of the creator (so you can vet them)

5. you should be able to add env vars