Menu

1 / 6

I wanted Copier in Rust, so I wrote rootstock

DEV Community: rust·Timur Lolaev·17 days ago
#fzEoiMed
#devtorust#devto#dev#template#rootstock
Reading 0:00
15s threshold

I write Rust for a living, and over the last couple of years the tools around me quietly turned into Rust too. On the frontend, Biome does what ESLint and Prettier used to. In Python land it's Ruff and uv. They're fast, they ship as one binary, and there's nothing to set up besides the binary itself.

Project templates were the exception. The best tool I know for them is Copier, and it's genuinely good. But it's Python, so every machine and every CI job that touches a template needs Python and pipx first. I wanted the same thing as one binary. That's rootstock.

Creating a project is the easy part

Plenty of tools can create a project from a template: cargo-generate, kickstart, cookiecutter. They render the files and that's it. From then on the project and the template live separate lives.

That's fine for a one-off. It hurts when the template keeps changing. Think shared CI workflows, lint configs, a service skeleton your team uses everywhere.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.