Use our flexible, scalable NoSQL cloud database [called Firestore] to store and sync data for client- and server-side development.
Getting back to what the actual post was about, my first instinct is to find out a way to replace Firebase/Firestore as a dependency of Firetable though -- does anyone know of any API-compatible replacements for Firebase with pluggable backends (minio[0] is to S3 as <something> is to Firebase/Firestore).
I also... kind of think this might be good tech to spin a whole SaaS out of. It'd be unthinkable to try and compete with Airtable if I had to build their frontend but... hosting a database, giving access to shared/private instances of firetable, and trying to out-maneuver (or just undercut) airtable seems like it might not be a completely fool's errand.
Really great to have something that feels a lot like Airtable open source. If I had a wish I'd say decouple the database layer instead of providing support for more databases. Let the community help build abstractions and that way also open Firetable for non-public or embedded data stores/ data bases.
It definitely might be the closest in spirit, but if the idea is just read and write documents in a document store, there is a lot of value in extracting the interface and allowing for multiple implementations.
I am an expert yak shaver, so it would have probably been one of the first things on my mind.
Comments
For those who aren't necessarily familiar with "Firestore" (I'd heard of Firebase but didn't know what Firestore was): https://firebase.google.com/docs/firestore
Getting back to what the actual post was about, my first instinct is to find out a way to replace Firebase/Firestore as a dependency of Firetable though -- does anyone know of any API-compatible replacements for Firebase with pluggable backends (minio[0] is to S3 as <something> is to Firebase/Firestore).
I also... kind of think this might be good tech to spin a whole SaaS out of. It'd be unthinkable to try and compete with Airtable if I had to build their frontend but... hosting a database, giving access to shared/private instances of firetable, and trying to out-maneuver (or just undercut) airtable seems like it might not be a completely fool's errand.
[0]: https://min.io/
Shams, the creator here. We built the MVP using Firestore but support for other DBs are on the roadmap.
Just want to say thanks for open sourcing this, there is an immense amount of value in here, surprised no one at Antler wanted to productize this!
should you exclude files such as https://github.com/AntlerVC/firetable/blob/master/www/.env.e... from the repo?
Its encrypted
Really great to have something that feels a lot like Airtable open source. If I had a wish I'd say decouple the database layer instead of providing support for more databases. Let the community help build abstractions and that way also open Firetable for non-public or embedded data stores/ data bases.
This is amazing! I'd suggest keeping focusing on Firestore until PMF and than expand to other dbs.
CouchDB: its APIs are not a 1-1 match but it feels the closest in spirit. Would love to know if there is another one.
It definitely might be the closest in spirit, but if the idea is just read and write documents in a document store, there is a lot of value in extracting the interface and allowing for multiple implementations.
I am an expert yak shaver, so it would have probably been one of the first things on my mind.