Hey y'all! Currently investigating benefits of monorepo in civic tech space: we do smaller but a lot of data/API-driven web apps. No prior experience with monorepos (or luxury of a dedicated team to manage them) and thus Pants feels like a good first step for the managing back-end related code. ❤️ the recent improvements around Python+Docker deployments. 🚀

You'll be happy to know we're working on more of those improvements!

Hey Carina. A bit slow (current/new work getting in the way!) but things are starting to make sense to the team. If my memory doesn't fail me, the only real issue right now is how to (elegantly) handle switching dependencies that are usually built for prod vs using pre-built binaries at dev e.g.

psycopg2

at prod,

psycopg2-binary

at dev. We initially looked at Bazel but their Docker support + the level where the tool makes sense seemed like it's meant for a much bigger team than ours. So, in short, we are currently investigating a 2 monorepos strategy: 1. API: back-end code, mostly Python, managed by Pantsbuild, and 2. UI: front-end code, mostly Nextjs, managed by Turborepo.

That makes sense. Ultimately we do want to add JS/TS support to Pants so that folks like you can use one tool for building everything.