The Spark Behind Bolt Orchestrator
I wanted to move super fast, but it's easy to lose track of spending, and configuring a new ignore file every time is a real time sink. Plus, when you update a Supabase Edge Function, new bugs can pop up, and without a solid branch system, you could lose those stable previous versions.
That's why I cooked up Bolt Orchestrator. My goal was to save Bolt Vibe Coders time, money, and headaches. It's a simple but powerful tool that'll save you a ton of pain if you use it right.
What It Does
You can give Bolt Orchestrator your GitHub and Supabase access tokens. This lets it quickly update the ignore files for your Bolt projects synced with GitHub and deploy any Edge Functions you've written with Bolt.
You can also toss in a Gemini/AI Studio API key. This allows it to use the latest Flash model and get suggestions on which files or folders to keep and which ones to ignore. Pretty neat, right?
How I Built It
Easy peasy! I used Claude as my consultant, and we whipped up a plan in just a few minutes. Then, I handed that plan over to Bolt, and boom! That's it! V1 was ready. Suddenly, I could rapidly update my Bolt project's ignore file with ease.
After running into other annoyances, like not having enough control over what got deployed to Supabase and having to manually dig through my directory tree to find what I wanted to ignore or keep, I "vibe coded" the new functionalities and slapped on the Bolt Logo.
Bumps in the Road
I kept getting these annoying CORS errors when trying to use some APIs from the frontend. So, I had to convert the React app into a Next.js app and then iron out some build errors.
Also, some features were just working in a clunky, unintuitive way. But by explaining exactly what was happening and what I expected, Bolt was able to sort out the issues.
What We're Pumped About
I'm not proud of this tool just because I built it in a few days. I'm proud because I actually iterated on my own pain points, and it genuinely solved my problem. It's so much easier for me to start new projects now, and I can even split a project into multiple branches without spending hours just prepping the environments.
Plus, all my development is backed up on GitHub. So, even if the app went down a path I didn't like, I just learn from my mistakes, start working on a new branch with a better plan, and delete the old branch and Edge Functions (or roll them back).
Key Takeaways
Always have backups and an easy way to roll back. That way, you can try more new stuff with confidence, without spending ages sorting out bugs and fixing bad user experiences.
What's Next for Bolt Orchestrator
For now, I'm making the app free and public. I want everyone at the Hackathon to be able to use it and get the most out of it! As I run into new challenges and issues during the Hackathon, I'll be adding more features. But for now, I think it'll help people save money, give the AI the right context, and most importantly, save them a ton of time.
Built With
- next.js
Log in or sign up for Devpost to join the conversation.