Skip to content

Turn into a copier template #30

@mdtanker

Description

@mdtanker

As I update this template, I need to then go and manually update all the repositories that I've created through this template. If instead this were a copier/cookiecutter/cruft template, I think it can be configured to propagate changes to the repos created from this.

Copier

  • template with built in support for users to update to new template versions
  • during generation makes a .copier-answers.yml file, which allows users to perform updates.

Cookiecutter

  • just a template, but allows updating if you use the 3rd party package cruft

Comparison between Copier, Cookiecutter, and Yeoman.

  • copier uses single YAML file while cookiecutter uses single JSON

From the Scientific Python Developers guide discussing their cookie template: "Much better interface with copier [compared to cruft], including validation, descriptive text, arrow selection, etc."

I think the concensus is copier is preferred over cookiecutter w/ cruft.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions