The Supabase comparison is pretty poor and needs improvement. In many ways TrailBase and PocketBase are architecturally a lot similar. The key-difference of both compared to Supabase is that they're a single executable, easy to self-host, less resource hungry and in many cases faster (for better or worse due to their simpler architecture). In case you're interested: https://trailbase.io/reference/benchmarks/
Privacy, data ownership and reduced reliance on public clouds were definitely motivations.
A Java/Kotlin client is certainly on the short-list. We recently added one for Swift. There are also clients for Dart, TypeScript, and C# in case you're more into cross-platform app development (Flutter, React Native, and Maui/Avalonia respectively)
Sorry to hear. The beauty of giving folks admin access and that's why we can't have nice things :). Excuses aside, in case you're still interested maybe try a bit later. The demo resets regularly. If you still run into issue, please don't hesitate to send a quick, low-key bug report: https://github.com/trailbaseio/trailbase/issues . Strong wording welcome
sounds like a nice side project for myself / something new (wth is that hype on Firebase and alternatives?) to look into on weekend like create per-user (likely with some limit of total 10 or so instance) demo env - average sysadmin like me should be able to handle it.
If i'll do something, will let you know if you wish
It's mostly about communicating the intend and a testament to Firebase establishing this rather broad product category, i.e. DB + dashboard + auth + files + ... You could probably also call it "a bucket of generally useful stuff", just doesn't have the same ring :).
> create per-user (likely with some limit of total 10 or so instance) demo env - average sysadmin like me should be able to handle it.
Totally feasible. There are also kubernetes deployment manifests in the repo. That said, I don't mind the shared instance too much. There's pros and cons. Happy to chat more.
> If i'll do something, will let you know if you wish
I think it's fair criticism and certainly an area where TrailBase can improve (it's still young). FWIW, I used to avoid the "Firebase" comparison and be more descriptive with a long list of features. That confused a lot of folks. Firebase-like seemed to get the rough product-ballpark across more effectively. If I had to guess, I'd say Supabase probably arrived at a similar conclusion.
Either way, they are all rather broad products and many users only use subsets.
Thanks for speaking up, appreciated.
Fwiw I changed my mind and I now think that your positioning is fine (see adjacent comment). Don't make it harder for people to grok at the behest of HN purists like me! :-)
Sorry, this is folks logging in and changing the password. Should have seen this coming :hide:. Instance gets reset every 60min. Not great but something to improve
Sorry, this is folks logging in and changing the password. Should have seen this coming :hide:. Instance gets reset every 60min. Not great but something to improve
:hide: thanks for pointing out this embarrassing plunder. No excuse, just feeling silly especially after being so careful throughout the rust base. It's fixed now. Please keep yelling if you find more issues
That type stinks. Kill the undefined bit by giving it an initial value, then you can skip the `?? []` later too; and replace Array<object> with the actual row type, probably naming it, maybe like this:
type Record = [string, number, number, number, number];
const [data, setData] = useState<Record[]>([]);
const params = new URLSearchParams({ aroma, flavor, acidity, sweetness });
I confess I’m puzzled about this one too, as trailbase.js suggests you know about URLSearchParams, which is what you should use for all typical query string manipulation, parsing and generation.