Appsmith

Try it for free at appomate.ai.

For a B2C AI SaaS product, the need to route every request via the backend (to protect keys) is one of the hurdles in offering low-latency experiences. The only solution is to ask the user to bring their own keys, which is a poor UX requiring them to sign up with each separate provider.

Anyone's got a better idea?

After wasting two weeks on this, now they confirm that a named Firestore database is not supported with Storage rules. Seems like it's a known issue, and it's nowhere in the docs!

Firebase Support Initial response:

From what I see at the moment I’m not entirely sure to say that only default databases can be used in such a situation. Given that you specify the full path in firestore.exists(/databases/(default)/documents/users/$(uid));, I'd expect that you can replace (default) with the database ID that you want to access. If you can't get that to work, we need to check it with a minimal repro.

Firebase Support final response:

In the end it turned out that at the moment Firestore non-default database is indeed not supported. I hope this will change soon, because we have more people with a similar problem like yours.

Has anyone been able to implement Cloud Storage security rules using permissions defined in a named Firestore database?

I just cannot get it to work, and cannot find anything in the docs.

I do see examples of using firestore.get() from the storage rules, but only for the default database, like here:

https://firebase.google.com/docs/storage/security/rules-conditions

Connected to an unsecured WIFi network last week from my MacBook. When I restarted I couldn’t login and had to go through safe/recovery mode and use reset password utility from the terminal to get back in (thankfully I could log in to my Apple ID.

Now I’m not able to login to my Firebase console even from another laptop.

What’s going on here?

Came across a post on X today touting this as something awesome and it's definitely not!

May be I'm too old school, but imho if you need to call an LLM to write a commit message you're not committed enough! I think commits ought to be granular and cohesive enough that you can describe in a line or two. And taking time to summarize what you've done is only gonna help you in the future.

WDYT?