Show HN: Mithril fork with Signals, state, store and SSR
* Repo: https://github.com/bitstillery/mithril
* Docs: https://mithril.garage44.org
* Repo: https://github.com/bitstillery/mithril
* Docs: https://mithril.garage44.org
Stack: - UV (Python package manager - incredibly fast) - FastAPI with full async/await - PostgreSQL triggers + LISTEN/NOTIFY for pub/sub - Bun for frontend builds - Proper connection pooling and lifecycle management
GitHub: https://github.com/garage44/plank
This came from rebuilding the same pattern across projects. Most examples I found were toy demos that didn't handle reconnection, dead clients, or proper shutdown.
Includes working frontend example that updates in real-time when database changes. Docker Compose setup for testing.
Good for: admin dashboards, monitoring tools, collaborative apps where you just need current state pushed immediately. Not for: guaranteed message delivery or job queues.
What I'm building: Codebrew is an AI-powered development workflow tool that aims to automate ticket management, code reviews, and time tracking. It's part of a planned ecosystem alongside two other tools I've been developing: Pyrite (real-time collaboration) and Expressio (i18n automation).
Current status:
• Expressio: Working alpha (https://codeberg.org/garage44/workspace/src/branch/main/pack...) - Automatic i18n with DeepL - Built with Bun - Already being used in small projects
• Pyrite: Being refactored - Moving from Vue to Preact - Real-time collaboration platform - Built on Galène SFU
• Codebrew: Early development - Integrating Claude for ticket refinement - Building Wakapi integration for time tracking - Planning GitHub/GitLab/Forgejo integrations
Tech stack:
• Backend: Bun/Node.js
• Frontend: Preact
• AI: Claude/Anthropic
• All open-source under MIT license
Why I'm building this: As a solo developer, I found myself spending too much time on routine tasks. While there are many great tools out there, they often feel disconnected or too complex for smaller teams. I'm aiming for something that's both powerful and lightweight.
The vision:
1. Keep each tool useful on its own
2. Build toward optional integration (project name: Nexus)
3. Focus on developer experience and automation
4. Stay open-source while building sustainable features
Looking for:
• Feedback on the architecture and approach
• Potential early adopters/testers
• Contributors interested in any of the components
• Thoughts on what features would be most valuable
Links:
• Workspace: https://codeberg.org/garage44/garage44
• Expressio docs: https://codeberg.org/garage44/garage44/src/branch/main/packa...
• Development blog: https://garage44.org
I know it's early days, but I believe in building in public and would love to hear your thoughts, especially from developers who've faced similar challenges in their workflows.