cookiecutter VS cookiecutter-golang

Sometimes I use this to abstract boilerplate https://github.com/cookiecutter/cookiecutter

It can use a repo as a template.

It supports some interactive questions to choose options but mostly it is jinja templates.

Having libraries would be another option.

Install the cookiecutter package using the following command:

Consider taking a look at cookiecutter to generate projects from templates. There is also cookiecutter-django. As for your environment variables you should have an example .env file containing all the environment variables required by your project (without setting them) that can be safely pushed into your repository for you and other developers to copy into the actual .env file that'll be used by your project (add this file to .gitignore)

The Python Cookiecutter library revolutionizes project development by offering streamlined approach to creating template projects and improving developer experience.

We use cookie cutter templates (the Python project, https://github.com/cookiecutter/cookiecutter ), we prompt for the module & version etc

Why not use cookiecutter or a similar tool designed for making these sorts of project templates?

Is it common? I don't know. Is it useful? Absolutely. There is a tool called cookiecutter that allows you to define your own setup. For example, my cookiecutter setup for a python library is here. You can see what it's like by first installing the cookiecutter cli and then running

Also cookiecutter.

Visual Cookiecutter enhances the functionality of cookiecutter by offering unique features such as required fields, conditional input parameters, optional descriptions, and the ability to fix mistakes easily. This package seamlessly integrates with cookiecutter so that all existing templates work out-of-the-box.

~ cookiecutter https://github.com/lacion/cookiecutter-golang.git full_name [Luis Morales]: Ricardo Castro github_username [lacion]: mccricardo app_name [mygolangproject]: demo project_short_description [A Golang project.]: A demo docker_hub_username [lacion]: mccricardo docker_image [lacion/alpine-base-image:latest]: golang:1.16.5-apline3.14 docker_build_image [lacion/alpine-golang-buildimage]: golang:1.16.5-apline3.14 Select docker_build_image_version: 1 - 1.13 2 - 1.12.9 3 - 1.11.9 Choose from 1, 2, 3 [1]: 1 Select go_mod_or_dep: 1 - mod 2 - dep Choose from 1, 2 [1]: 1 use_docker [y]: y use_git [y]: y use_logrus_logging [y]: y use_viper_config [y]: y use_cobra_cmd [y]: y Select use_ci: 1 - travis 2 - circle 3 - none Choose from 1, 2, 3 [1]: 3 Initialized empty Git repository in /home/mccricardo/test/demo/.git/ [master (root-commit) 2e82ac9] Initial Commit. 13 files changed, 597 insertions(+) create mode 100644 .gitignore create mode 100644 AUTHORS.md create mode 100644 CONTRIBUTING.md create mode 100644 Dockerfile create mode 100644 Makefile create mode 100644 README.md create mode 100644 cmd/root.go create mode 100644 cmd/version.go create mode 100644 config/config.go create mode 100644 go.mod create mode 100644 log/log.go create mode 100644 main.go create mode 100644 version/version.go

@backstage/plugin-scaffolder-backend through CookieCutter "knows" how to bootstrap Golang projects based on cookiecutter-golang. And that's how all the magic happens.