When you're fullstack and solo, every side project is really two projects. a backend repo, a frontend repo, an API between them, auth crossing that boundary, two deploys that have to move together. and you're the whole team for both. i kept seeing posts here about how "fullstack" keeps expanding into doing everyone's job, and honestly for indie projects i felt that the most in the glue work, not the actual features.
so back in August 2022 I started a project called fymo, to make one-repo Python+Svelte projects a normal thing to build. got stuck early, compiling Svelte from Python and making the two sides talk to each other was beyond me then, so it sat there for a while, like my other side projects did. between years, i came back and forth, but this time it stuck, and I finished it.
the shape of it: Python renders real Svelte 5 components, controllers return dicts that land in components as props, and Python functions become typed functions you import in Svelte, so no serializer, no endpoint, no fetch code. fymo new gives a running app with sign in, fymo generate resource posts gives a routed page, CRUD endpoints and passing tests. one repo, one deploy.
it's v0.20, one maintainer, needs Node installed, no ORM. things still break between versions, loudly though.
Repo: https://github.com/Bishwas-py/fymo -> pip install fymo
curious how other solo devs handle this though. do you just eat the two-repo cost, use a monorepo with turborepo or something, or collapse the stack some other way? genuinely asking, because the glue work is where my projects used to die.
