56bf7c379c
Developers run all sorts of different tools within Git repositories, any of which can leave their own special trashfiles all over the place. We can't every hope to catalog them all, so better to recommend developers simply configure a global core.excludesfile to filter the irrelevant files which tend to get created by their personal choice of tools. Add a comment block explaining this, for clarity. We can, and should of course, continue to list files created by the tools recommended by our workflow (test frameworks, documentation and packaging builds, et cetera). This change is a port of Ib58a57267b064e4142686de6c37a70dbff04b9a7 from the openstack-dev/cookiecutter repository. Change-Id: Ia1da64c08247ea7f8a8b4b3677fe65ae45455c3b |
||
---|---|---|
puppet-{{cookiecutter.project_name}} | ||
.gitreview | ||
LICENSE | ||
README.md | ||
cookiecutter.json |
README.md
puppet-infra-cookiecutter
Cookiecutter template for a compliant OpenStack-infra puppet-modules
Installation
Install cookiecutter either from source, pip or package if it exists
Usage
There are two ways to create the boilerplate for the puppet module.
Locally
- Clone locally the puppet-infra-cookiecutter repository.
- Run
cookiecutter /path/to/cloned/repo
Remotely (ie. using a git repo)
- Run
cookiecutter https://git.openstack.org/openstack-infra/puppet-infra-cookiecutter.git