📁 my_copier_template # your template project
├── 📄 copier.yml # your template configuration
├── 📁 .git/ # your template is a Git repository
├── 📁 {{project_name}} # a folder with a templated name
│ └── 📄 {{module_name}}.py.jinja # a file with a templated name
└── 📄 {{_copier_conf.answers_file}}.jinja # answers are recorded here
from copier import run_copy
# Create a project from a local path
run_copy("path/to/project/template", "path/to/destination")
# Or from a Git URL.
run_copy("https://github.com/copier-org/copier.git", "path/to/destination")
# You can also use "gh:" as a shortcut of "https://github.com/"
run_copy("gh:copier-org/copier.git", "path/to/destination")
# Or "gl:" as a shortcut of "https://gitlab.com/"
run_copy("gl:copier-org/copier.git", "path/to/destination")
Basic concepts
Copier is composed of these main concepts:
Templates. They lay out how to generate the subproject.
Questionnaires. They are configured in the template. Answers are used to generate
projects.
Projects. This is where your real program lives. But it is usually generated
and/or updated from a template.
Copier targets these main human audiences:
Template creators. Programmers that repeat code too much and prefer a tool to do
it for them.
Tip: Copier doesn't replace the DRY principle... but sometimes you simply
can't be DRY and you need a DRYing machine...
Template consumers. Programmers that want to start a new project quickly, or
that want to evolve it comfortably.
Non-humans should be happy also by using Copier's CLI or API, as long as their
expectations are the same as for those humans... and as long as they have feelings.
Templates have these goals:
Code scaffolding. Help
consumers have a working source code tree as quickly as possible. All templates allow
scaffolding.
Code lifecycle management. When the template evolves, let consumers update their
projects. Not all templates allow updating.
Copier tries to have a smooth learning curve that lets you create simple templates that
can evolve into complex ones as needed.
Browse or tag public templates
You can browse public Copier templates on GitHub using
the copier-template topic. Use them as
inspiration!
If you want your template to appear in that list, just add the topic to it! 🏷
Show your support
If you're using Copier, consider adding the Copier badge to your project's README.md:
Special thanks go to jpsca for originally creating Copier.
This project would not be a thing without him.
Many thanks to pykong who took over maintainership on the
project, promoted it, and laid out the bases of what the project is today.
Big thanks also go to yajo for his relentless zest for
improving Copier even further.
Thanks a lot, pawamoy for polishing very important rough
edges and improving the documentation and UX a lot.
Also special thanks to sisp for being very helpful in
polishing documentation, fixing bugs, helping the community and cleaning up the
codebase.
And thanks to all financial supporters and folks that give us a shiny star! ⭐
FAQs
A library for rendering project templates.
We found that copier demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Malicious Go packages are impersonating popular libraries to install hidden loader malware on Linux and macOS, targeting developers with obfuscated payloads.
Bybit's $1.46B hack by North Korea's Lazarus Group pushes 2025 crypto losses to $1.6B in just two months, already surpassing all of 2024's $1.49B total.
OpenSSF has published OSPS Baseline, an initiative designed to establish a minimum set of security-related best practices for open source software projects.