Advanced Usage

Using Pre/Post-Generate Hooks (0.7.0+)

You can have Python or Shell scripts that run before and/or after your project is generated.

Put them in hooks/ like this:

├── {{cookiecutter.repo_name}}/
├── hooks
│   ├──
│   └──
└── cookiecutter.json

Shell scripts work similarly:

├── {{cookiecutter.repo_name}}/
├── hooks
│   ├──
│   └──
└── cookiecutter.json

It shouldn’t be too hard to extend Cookiecutter to work with other types of scripts too. Pull requests are welcome.

For portability, you should use Python scripts (with extension .py) for your hooks, as these can be run on any platform. However, if you intend for your template to only be run on a single platform, a shell script (or .bat file on Windows) can be a quicker alternative.

User Config (0.7.0+)

If you use Cookiecutter a lot, you’ll find it useful to have a .cookiecutterrc file in your home directory like this:

    full_name: "Audrey Roy"
    email: ""
    github_username: "audreyr"
cookiecutters_dir: "/home/audreyr/my-custom-cookiecutters-dir/"

Possible settings are:

  • default_context: A list of key/value pairs that you want injected as context whenever you generate a project with Cookiecutter. These values are treated like the defaults in cookiecutter.json, upon generation of any project.
  • cookiecutters_dir: Directory where your cookiecutters are cloned to when you use Cookiecutter with a repo argument.
  • abbreviations: A list of abbreviations for cookiecutters. Abbreviations can be simple aliases for a repo name, or can be used as a prefix, in the form abbr:suffix. Any suffix will be inserted into the expansion in place of the text {0}, using standard Python string formatting. With the above aliases, you could use the cookiecutter-pypackage template simply by saying cookiecutter pp, or cookiecutter gh:audreyr/cookiecutter-pypackage. The gh (github) and bb (bitbucket) abbreviations shown above are actually built in, and can be used without defining them yourself.

Calling Cookiecutter Functions From Python

You can use Cookiecutter from Python:

from cookiecutter.main import cookiecutter

# Create project from the cookiecutter-pypackage/ template

# Create project from the cookiecutter-pypackage.git repo template

This is useful if, for example, you’re writing a web framework and need to provide developers with a tool similar to startproject or npm init.

Injecting Extra Context

You can specify an extra_context dictionary that will override values from cookiecutter.json or .cookiecutterrc:

             extra_context={'project_name': 'TheGreatest'})

Example: Injecting a Timestamp

This is a sample Python script that dynamically injects a timestamp value as a project is generated:

from cookiecutter.main import cookiecutter

from datetime import datetime

    extra_context={'timestamp': datetime.utcnow().isoformat()}

How this works:

  1. The script uses datetime to get the current UTC time in ISO format.
  2. To generate the project, cookiecutter() is called, passing the timestamp in as context via the extra_context dict.

Suppressing Command-Line Prompts

To suppress the prompts asking for input, use no_input.

Basic Example: Using the Defaults

TODO: document no_input:

  • As command-line argument
  • As parameter of cookiecutter()

TODO: document where context values come from in this example (cookiecutter.json and .cookiecutterrc)

Advanced Example: Defaults + Extra Context

If you combine an extra_context dict with the no_input argument, you can programmatically create the project with a set list of context parameters and without any command line prompts:

             extra_context={'project_name': 'TheGreatest'})

See the API Reference for more details.

Command Line Options

-h, --help

show this help message and exit


Do not prompt for parameters and only use cookiecutter.json file content

-c, --checkout

branch, tag or commit to checkout after git clone

-V, --version

Show version information and exit.

-v, --verbose

Print debug information