cookiecutter VS backstage

Visit the project's repository on GitHub

Personally, I have a really good set of makefiles that do all of the work (creating pdf/HTML to creating packages for PyPI and uploading). I have a few cookiecutter repos set up to simplify the boilerplate and ease new projects.

It's nice but, usually, Django folks tend to use cookiecutter (https://github.com/cookiecutter/cookiecutter) for this kind of 'templating' a project.

Have a look at cookiecutter as well - https://github.com/cookiecutter/cookiecutter

If you’re any way like me, then you must automate a task when you find yourself doing it more than once. I’ve automated the creation and configuration of a modern Python project using cookiecutter. You will need to set up your environment first. Also, nitpick uses my own take on the wemake-services configuration, you can view the repository here.

https://github.com/cookiecutter/cookiecutter and the related https://github.com/feldroy/django-crash-starter seem somewhat active and current.

Trust me, I have no desire to write a custom tool, it's always my last resort. I'm wondering if there's something in between pulling existing files from a repo and a custom tool. Something like cookiecutter but which has more fine-grained control with what it pulls down (i.e. I don't want to create an entire starter project, just something like tool pull precommit-python [optional args]).

Ideally, build your own cookiecutter.

Looks great, good job, what do you think of using something like https://github.com/cookiecutter/cookiecutter ?

Backstage is a large project with lots of backend modules that might be helpful reference. Check out the “*-backend” packages in the plugins folder. https://github.com/backstage/backstage

I've been meaning to give this a try https://backstage.io/

A software system often contains multiple components such as backend services, database, API, documentation, etc. Is usually hard for us to have an overview, such as how many components we have? which component is connected to which? Who is the owner? Where can I find the documentation? Where can I see the API? etc. One way to solve this problem is to build a catalog for our infrastructure. We can achieve this quickly with the help of Backstage.

Dive straight in the repo 🤿 at GitHub

Learn more about Backstage 🙌🏻 at the project website

The next iteration is to integrate with a service catalog using Backstage to manage service, owners, and product flows as they pertain to both business and incident management: https://github.com/backstage/backstage

https://backstage.io is exactly what you need. It actually got me to finally learn typescript ;)

I can recommend looking at https://backstage.io. This came out of spotify to solve the entire company portal thing. It's very nice and customizable. So nice in fact that I finally started learning TypeScript just so I can build out plugins for it.

If you have an opportunity to make some changes check out Backstage