New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attachment replication with Firebase Storage #5766
Comments
Hi @FathiGuemri |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. If you still have a problem, make a PR with a test case or to prove that you have tried to fix the problem. Notice that only bugs in the rxdb premium plugins are ensured to be fixed by the maintainer. Everything else is expected to be fixed by the community, likely you must fix it by yourself. |
Issues are autoclosed after some time. If you still have a problem, make a PR with a test case or to prove that you have tried to fix the problem. |
After confirming that RxDB does not support attachment replication with Firebase Storage, I set up a manual method to enable it. However, suddenly RxDB supports attachment replication, but only within the same database, which is somewhat good. However, it will affect the database size and its cost significantly for Firestore.
Is there a plan in the future to enable attachment replication with Firebase Storage and others like Amazon S3, Google Cloud Storage, Microsoft Azure Blob Storage...?
I expect it to be quite simple. Instead of storing attachments in the database, they can be uploaded to Firebase Storage.
I tried to create a pull request on the repository to enable this, but honestly, I'm new to replication protocol and lack understanding of the code. However, this my suggestion:
Add new option
attachmentWithFirebaseStorage
to the SyncOptionsFirestore type:export type SyncOptionsFirestore = Omit< ReplicationOptions, 'pull' | 'push' > & { firestore: FirestoreOptions; attachmentWithFirebaseStorage: FirebaseStorage; // this new option serverTimestampField?: string; pull?: FirestoreSyncPullOptions; push?: FirestoreSyncPushOptions; };
`The text was updated successfully, but these errors were encountered: