multiple firebase and supabase connections
It wasn't meant to be a complaint, more like a frustrated heads up. Happy to pay for a good product (even if my Firebase / Firestore doesn't work, like others: all requests and up in "not found, error 5").
A bit more information on the pricing would be benefitial, I am a Indy by night and Product Manager for App development by day, so perhaps my way of working is different than others, that's why I asked. I have a couple of smaller experiments and app projects running across multiple providers, and thought consolidating some projects into one Pro Plan will facilitate the backenend needs for all projects (I have a backend developer background, but I LOVE the light and crispyness of Rowy and Buildship for my backend needs, can't be bothered to do all the basework from scratch)
A folder structure would be a huge benefit for organzing different areas of your api.
I am still not sure how to deal with multiple data vendors, like multiple SB instances or using the build in FB instance with a Flutterflow project or not? Are there any best practises?
3 Replies
Great to hear you are enjoying using BuildShip and Rowy.
Reg the not found error, if you can share a bit more over email to support@buildship.com or via in app support we will get to the bottom of it, and cc @Gaurav Chadha who might be on it already
We are working on making pricing even more clear based on all these feedback so thats for that, really appreciate it. Folders coming real soon.
You should be able to connect to multiple FB - one way is to use the Rowy project connected to FB and calling a BuildShip trigger. cc @Bhavya ✨ do we have any examples of multiple FB projects connected to same BuildShip project and used via Firestore nodes?
For SB you can use the webhook API way if its a data/auth triggered event - for general CRUD too you can use the Supabase nodes to connect to multiple SB projects easily by create multiple secret keys.
Hey @HeikoK, we offer multiple methods for connecting different Firestore Projects to a single BuildShip Project:
- One approach is via the Firestore nodes available in the Node Library. These nodes include a Project ID field where you can specify the Firebase project's ID you intend to connect with. Note that you'll need to follow the steps outlined in this Firebase Integration tutorial for each project you wish to link to your BuildShip Project. You can use multiple Firestore nodes connected to various Firebase Projects within the same workflow.
- Another option involves connecting your BuildShip project to your Rowy Table associated with your Firestore Project using the Rowy Trigger (on BuildShip). This enables triggering workflows upon Create, Update, or Delete events in your Rowy table. Learn more about the Rowy Trigger in detail here.
NOTE: You can only have one Rowy trigger per workflow, but you can create multiple workflows with Rowy Trigger, each connecting to different Rowy Tables or Projects.
If you have any further questions, feel free to ping me and I can create a quick video showcasing this feature in depth! 😄
Thanks, I pinged @Gaurav again with the requested information
Thanks. It finally clicked with regards to adding Firebase projects. I was just blind and still had a 1:1 connection in my head (so only one BS project can be connected to ONE firestore project... that was wrong)