René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cookiecutter + Cruft Setup","articleBody":"Inspired by this [post](https://blog.wolt.com/engineering/2022/08/11/project-template-for-modern-python-packages/) detailing templating via [cookiecutter](https://cookiecutter.readthedocs.io/en/latest/) and [cruft](https://cruft.github.io/cruft/), would love to parameterize a good portion of this public template to make starting future Python projects less cumbersome.\r\n\r\nCurrent _okay_ method for creating a new repo:\r\n```bash\r\n# create repo from template\r\ngh repo create delete_moi --public --template \"pythoninthegrass/python_template\" \r\n\r\n# clone repo locally\r\ncd ~/git \u0026\u0026 gh repo clone delete_moi \u0026\u0026 cd delete_moi/\r\n\r\n# remove a bunch of irrelevant directories and files\r\nrm -rf terraform/ pyproject.toml poetry.lock requirements.txt startup.sh jupyter/\r\n\r\n# create new poetry project\r\npoetry init\r\n\r\n# create virtual environment with dependencies\r\npoetry install\r\n\r\n# export requirements.txt\r\npoetry export -f requirements.txt --output requirements.txt --without-hashes\r\n```\r\nTo be fair, also have Docker files that negate some of that. Using the #8 will help, but cookiecutter + cruft fill in the gaps for non-Docker scaffolding and syncing repos when upstream changes are made.","author":{"url":"https://github.com/pythoninthegrass","@type":"Person","name":"pythoninthegrass"},"datePublished":"2022-09-28T16:11:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/9/python_template/issues/9"}