Allow to use custom templates

[piranna]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

For the generate command, add a new --template CLI arg that would define what actual template to use, instead of just only the built-in ones. It can be a path to a local folder, so files would be copied from there instead of from the location of the built-in templates, or an url, so the content would be downloaded from there, for example from a git repository.

Motivation

I would like to have a pre-defined template with some custom plugins, and this way would be easier than using a cookies-cutter or an install script.

Example

No response

[sankalpaacharya]

If you want to download a template from GitHub or anywhere else online, why not just download it manually or use git clone?

Allowing the CLI to download arbitrary templates from the internet could introduce security risks and might reduce trust in the official Fastify CLI. Keeping template sources limited to local paths or verified built-in ones would help ensure users know exactly what code they’re running.

[piranna]

If you want to download a template from GitHub or anywhere else online, why not just download it manually or use git clone?

Because that would only be a copy, and later it would not be initialized with project name or so.

Allowing the CLI to download arbitrary templates from the internet could introduce security risks and might reduce trust in the official Fastify CLI. Keeping template sources limited to local paths or verified built-in ones would help ensure users know exactly what code they’re running.

There are several tools that allow to initialize projects from templates, without that problem at all. Code downloaded can also be inspected from their sources, and trust should go to the template publishers, not Fastify CLI devs...