Multiple database under app
- Langage dominant
- TypeScript
- Étoiles
- 7.8k
- Forks
- 2.2k
- Merge moyen
- 22 h 28 min
- PR mergées (30 j)
- 6
Description
Dear Angularfire!
I would like to ask if the application described below can be solved in any way.
So, I currently have 2 source codes with 2 firebase projects. Separate users and data for each project.
Thanks to a development, we are trying to unify the systems within the company.
**Consequently, the aim would be to:**
- `Application number one: We would not reach for this. Here will be the users and user permissions. for example: user.claims = 1 (admin)`
- `Delete users from the other application and set up the application 1 database. Only the admin can access this page.`
- `Application 1 would work in Firestore 1 and Application 2 would work in Firestore 2.`
- So far, I find this feasible.
- `How can I make sure in database 2 (firestore) to make sure the user has the right claims? Is it possible to move between projects in this way?`
Sorry if I'm not understandable, writing English is not my strength. If anything is not clear I will try to explain better.
**post: Most of Database 2 is completely public, unlike Database 1, which can only be viewed by a logged in user.**

Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Le rapport ne mentionne aucun fichier du dépôt, test ou point d’entrée. Commencez par examiner la configuration d’AngularFire et la prise en charge par Firebase de authentication/claims pour plusieurs projets ; le travail serait terminé lorsqu’une approche prise en charge ou une limitation clairement définie existerait.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, firebase, typescript
- Domaine
- authentication, database
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 15/100