Phase 2:
[x] custom_data incl bson support
[x] functions
[x] remote mongodb client
[ ] push
Details of above subtasks are described in this doc

The encryption section in Java docs https://realm.io/docs/java/latest/#encryption leads to an example that doesn't properly provide a best practice solution for how to store keys used for encryption.

Goals

Update code to npm install --save realm@5.0.0 at realm package installation instruction after switching to Realm JavaScript 5.0.0 Latest in the documentation.

Expected Results

npm install --save realm@5.0.0 at installation instruction of Realm JavaScript 5.0.0 Latest in the documentation.

Actual Results

Package installation with the instruction of 4.0.0beta version in the

Original title: 修改表字段的默认值问题

![image](https://user-images.gith

Phase 1:
[ ] provider clients (email-password)
[ ] link_user
[ ] custom_data

Phase 2:
[ ] remote mongodb client
[ ] functions
[ ] push
[ ] Remaining provider clients

Details of above subtasks are described in this doc

We currently only run a few select unittests with encryption - we should extend this so that all unittests are run with encryption, at least periodically (it takes a while, so may not be needed on PR's, but master once a day for example)

Need to include:

• Consul information
• Subdirectories for each section with package files
• Move over all code samples: https://docs.realm.io/platform/self-hosted/manage/enterprise-architecture/manual-deployment-instructions