You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the firebase database url is hardcoded to the production url. Ideally we would have a dev environment database when developing locally. I've never set up something like that using Firebase, so I'm not sure if that would entail using a shared dev database (not ideal, but simpler), or each developer using their own sandbox firebase instance (best option, but no clue how we would set that up).
The text was updated successfully, but these errors were encountered:
This hasn't been an issue so far. We could "namespace" the buckets by using a "production" ref for the production site. And then if we are developing, use a uuid.v4() as the namespace.
This scheme would use the same firebase data storage, but it would work.
For now, I'm just putting some thoughts here. We will revisit this when necessary.
Right now the firebase database url is hardcoded to the production url. Ideally we would have a dev environment database when developing locally. I've never set up something like that using Firebase, so I'm not sure if that would entail using a shared dev database (not ideal, but simpler), or each developer using their own sandbox firebase instance (best option, but no clue how we would set that up).
The text was updated successfully, but these errors were encountered: