Project templates with Cookiecuter
summary
Shows how to turn a live repo into a reusable template with Cookiecutter, using cookiecutter.json to validate variables and Jinja variables to render filenames and file contents, plus pre/post-generation hooks for dependency checks and cleanup. Recommends keeping template and example repo together, updating templates as projects evolve, swapping unit tests to pytest, adding Docker files and Make targets, extracting shared code to private libs, using direnv and a .env file to centralize environment variables and avoid human errors.
AI-written summary · about
chapters (12)
- 0:00Introduction and background
- 2:29Why use project templates
- 6:24What is Cookiecutter
- 10:12Creating your own template
- 14:09Converting project to template
- 18:36Iterating and improving templates
- 20:21Recap and next steps
- 21:06Making choices in templates
- 24:23Tools and alternatives
- 25:48Demos and resources
- 26:51Environment variables with dotenv
- 27:32Homework and closing
related talks
31mCome to the Dark Side! We have a whole bunch of Cookiecutters!
28mKickstarting projects with Cookiecutter
30mControl all of your projects with copier!
17mExemplar-y Backstage Templates
36mBuilding Docs like Code: Continuous Integration for Documentation
45mKeeping it DRYer with Templates
21mUsing CI Templates for Speed and Consistency
39mSharing Your Side Projects Online and Making Your Github the Best Résumé It Ca
