Atlas App Services
237 results found
-
Improve Realm Documentation for Various SDK Integrations
With existing examples and documentation about Realm SDK integrations was a bit confusing.
Example: React Native SDK - hard to find best example for offline first mobile app with realm (sync)
if we can have GitHub repo example integrations with minimal features for each SDK implementation it would really helpful for the community to find what they're looking for.
Contribution: communicate can contribute by giving an example for each or multiple feature implementation examples.
3 votes -
Allow community submissions to documentation
Let's face it, the Realm documentation as a whole is really lacking in comparison to the level of documentation of Atlas and other enterprise-level products. There have even been times I've had to search the old stitch documentation to understand how something works, and many other times I'm left experimenting or abandon a feature completely (for example, I gave up on Environments).
Other places have had success putting documentation on GitHub and allowing community submissions via pull requests.
Please allow the same -- I would happily contribute rather than needing to maintain my own notes (for me and my team)…
2 votes -
Increase max 100 item limit from Realm Logs API
Currently the API has a hard limit of returning 100 results. For any sort of real diagnostics with the logs, this is pretty much worthless -- with a large quantity of transactions, the only thing I can think of to do would be to write a script to loop through time intervals and aggregate them on my side.
As a real-world scenario, I was trying to identify the full scope of impact of a bug that went out and was not caught for a couple days and ran into the limit. It was also difficult to even identify exactly when…
2 votes -
Allow user-set 'deployment id/name' via realm-cli
We're using github actions to fully automate our realm deployments with the cli, and I'd like to be able to give a user-friendly name so that we can easily identify the currently deployed version (such as the git hash). Currently under "deployments" what I see looks like an internal realm deployment id.
1 vote -
Notification on function failure
I would like a notification if a trigger fires a function, and the function fails.
I have a scheduled trigger that calls a function every day. I have no idea if the function fails unless I manually log in and check the status. I would like to be alerted in the event of a failure. I've gotten around this by manually setting up Slack notifications.
19 votes -
Injection Attack Documentation
Hi MongoDB, we are in the process of preparing for production and while we have found some susceptibilities to injection attacks on mongodb (see OWASP Top 10) there does not seem to be any documentation explaining all the potential known avenues of attack for MongoDB. The response from the engineering team is there is shared responsibility, however, how can we share responsibility for what we do not know? We as engineers rely on the product owners to give known attack vectors so that we can share that responsibility.
That said, there are two we know about, escape for the $…
1 vote -
Support parquetjs or parquetjs-lite dependencies
Our product would like to read the parquet file-format from an S3 source. Both parquetjs and parquetjs-lite are incompatible with Realm's dependency upload.
parquetjs: "boto" module is a duplicate of a top-level Realm default library.
https://www.npmjs.com/package/parquetjsparquetjs-lite: Parse error when uploading tarball. See screenshot below.
https://www.npmjs.com/package/parquetjs-liteThank you!
3 votes -
Please write explicit rules for anonymous auth users deletion or provide controls to adjust the behavior
In the documentation for anonymous auth, it says that Realm may delete anonymous users that are 90 days old https://docs.mongodb.com/realm/authentication/anonymous/
There is also a mention about 30 days of inactivity https://developer.mongodb.com/community/forums/t/persisting-anonymous-users/10247/2?u=anton_p
That's hard to rely on something so broad to make decisions in the app logic. Is it possible to clarify this behavior or provide control over this flow?
4 votes -
Return the Webhook URL through the CLI
When creating a service Webhook through the CLI, return the Webhook URL through the CLI instead of requiring users to get it from the UI.
1 vote -
Increase RealmReturn Body Max Size
The maximum return body size of a realm webhook is 4MiB (4194304 bytes). That might seem enough for most applications but when dealing with massive amounts of data, e.g. timeseries data over years, that is a hard limitation.
It requires the client to make many more requests that would be necessary.In our special case we want to return one whole year worth of data per request to make things easier for our clients (currently they can get 3 months).
Given a 16MB Limit on a MongoDB Collection Document, this would seem like a sensable option for a limit if…
5 votesHi Marc – We have a ticket for this that’s near the top of the backlog and plan to increase the limit to 16MB in the near future.
-
Add Soap Npm Module
Pls support soap npm module for calling soap web service.
1 vote -
Sign in with Apple Server to Server Endpoint
It would be great if there would be an easier way to set up Apple's server to server notifications to deal with authorisation changes, user deletes etc. That would allow a user to sign out or delete their user through any device without having to login to the app.
1 vote -
Set custom endpoint for s3 service
Allow users to use a custom s3 endpoint for example: nyc3.digitaloceanspaces.com
1 vote -
Provide an access to the Objects defined by schemas
Currently, Realm-CLI provide a way to automate configuration deployment, but in case of change on the schemas, the objects defined in the "data-model" tab aren't accessible programmatically (i.e via CLI or API). I think it's an empidement to reaching full automation concerning schema definition.
1 vote -
Export/import users in Realm app
Option to export all Realm app users and import them.
It's a major concern that users can't be exported. Both for backup reasons and also for moving them between apps.
If you delete or loose a Realm app you are out of business because the users are gone and if you mistakenly chose the wrong deployment region, you can't move the app because you can't move the users.
I think this is absolutely critical to growing a business using Realm apps.
35 votes -
nodemailer Support
Nodemailer is currently not supported because of the punycode dependency. Would be nice to send mails directly on the mongodb server.
5 votes -
Custom OAuth 2 Providers
Allow us to input custom oauth2 providers for login. I know we can do something similar through custom functions, however, it would be nice if we can just add them easier.
1 vote -
Support mongoose
Add mongoose to Functions and a place to store mongoose Schemas,
Also, Realm UI Schema and authorization documentations are not very complete or clear
1 vote -
Add Refresh Button in Realm UI Logs Section
Having a refresh button on the Logs section of Realm UI will be amazing, just like the one on the MongoDB collections on the Web version
1 vote -
Add more documentation about schema changes
I made a substantial change to my schema that was not covered in the existing documentation. I resolved the problem based upon the information Ian Ward gave in this thread: https://developer.mongodb.com/community/forums/t/performing-destructive-changes-to-synced-realm/10757/11. This really should be in the documentation.
1 vote
- Don't see your idea?