Atlas App Services
234 results found
-
FTP Access to Realm Hosting
Uploading web apps into the hosting directory can be time consuming using only the ATLAS UI - specifically because the UI/UX does not support uploading entire folders. This means you have to re-create the folder structure, and upload specific files into specific folders rather than just uploading a single folder with all folders/subfolders.
This problem could be easily solved by providing FTP access to the "hosting" section.
1 vote -
Realm sessions
Could you please add a "remember me" or option for longer sessions on the Realm / Atlas Web UI?
Besides the annoying factor of daily/24h re-sign-in, a couple of times I lost function changes when working in a tab that was left open overnight and a save would fail due to a stale session.1 vote -
List databases and collections from Atlas data api
Ability to discover databases and their collections from the Atlas data api.
4 votes -
Atlas Realm deployments to Canadian Datacenter
We would like a deployment of Realm in a canadian datacenter either in AWS or Google Cloud.
1 vote -
Additional Filters to App Users Page
Add additional filtering capabilities to the "App Users" page. Currently you can only by "id". Im not sure if its due to our app setup but the "id" seems like a totally random generated id that is not associated to any data in our DB. It would be nice to filter based on name, createdTime, last login time, etc instead of just id
1 vote -
Ensure Realm Documentation Matches Implementation
"Int" is listed as a supported type for partition keys but it's not implemented. You should remove "Int" from the supported types since it's not supported.
1 vote -
Support for dynamic Open Graph Protocol meta tags
Ability to whitelist certain IP addresses for social media crawlers and send them to a function that does server-side rendering of the index.html page to create open graph protocol (https://ogp.me/) meta tags for a dynamic link preview depending on what the link is. This specifically applies for single-page webapps.
1 vote -
Link Two Email Credentials
Should be able to link two or (preferably) more different email address credentials to 1 realm user.
Most obvious use case for this would be an app that has both a business domain, and a personal domain. The user can log in to their realm account with either their personal email addresses or their business email addresses.
1 vote -
Realm Trigger Event Projection should support exclusion
Realm triggers with a projections must include "operationType": 1. This makes excluding fields impossible because, according to the documentation:
if you exclude fields, you cannot also specify the inclusion of fields
The only work around we have found is to list every single field in the database and this would require an update anytime we add another field to the model. This is quite cumbersome and should be easily resolved with a simple exclusion.
7 votes -
Disable/Enable all triggers at once
It would be very useful to be able to disable/enable all triggers of realm application at once. It useful for instance when you restore data from backup or make some big changes, and it is not needed to run triggers on every change
1 vote -
1 vote
-
Support of dependencies which rely on an extra binary
We would like to establish connection to OracleDB from a REAM Function. For that we're using
oracledbnpm module.However this module is dependent on a third party binary (Oracle Instant Client “Basic” or “Basic Light” package), which should be in the PATH and located by the npm module.
Can REALM add support of this feature?
3 votes -
changeEvent cluster name
I want to be able to programmatically access the clusterName from change event or global variable for example:
changeEvent.ns.cluster = <CLUSTER/SERVICE name>
global.CLUSTER_NAMEI need this when I want to perform an update on same collection/document after the trigger, but i don't want to hardcode the clusterName - because i have multiple environments - each has its own cluster (dev/sandbox/prod etc...)
1 vote -
One-time scheduled triggers
At the moment, MongoDb offers the ability to schedule triggers periodically using Cron Jobs. It would be really handy if a user could schedule a trigger to run only once and execute a function as my use-case requires.
1 vote -
Need more close realm server in Asia
currently realm server which can use in Asia is too far and limited like below link
https://docs.mongodb.com/realm/admin/deployment-models-and-regions/#cloud-deployment-regions
so, i think it has some delay to request realm server as well as management using realm web UI
it would be nice to be able to use more close server19 votesWe have started work on more regions as well as cloud providers.
-
Terraform Provider
It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.
13 votes -
Containerized Functions + Logging + Dependencies Improvements
I believe most of the below asks would be resolved if you allowed containerized functions to be uploaded and we can have the correct execution environment.
Allow larger function sizes
Allow more larger dependency sizes
Allow 256kb size per log entry
Allow Unlimited log entries per function execution
Output formatted logs, don't want to scroll right forever
Add refresh button for logs
Log arguments for triggered function automatically
Don't truncate logs
Allow logs to be streamed so that you don't need to refresh logs
Increase execution time to 15-30 minutes
Allow dependencies to be imported outside of function definition
Allow…1 vote -
GitHub Deploy - pulling deletes standard files, like LICENSE, README.md, etc.
If I make a change in the UI, deploy, then do a git pull on my local machine, the pull deletes my License, README.md, and .gitignore files. These are standard files and should not be changed on pull. It's like it's overwriting everything from scratch instead of just doing a diff. My repo is public and I need to include this basic info.
1 vote -
Allow for Name filtering in REALM logs
Currently Realm logs are pretty limited in functionality. It is hard to sort, filter and track down a specific log file. A filter option based on name would be beneficial. The filter could show all of the recent runs of something based on the name. Also, it would be nice to see the log pages refresh automatically.
4 votes -
Add retry policy to Atlas Trigger
A failed Atlas trigger gets suspended and will not retry without manual intervention. Some transient conditions can be retried and it would be useful to configure a retry policy with a trigger (at the Realm Function level). Retry X times with Y back-off seconds between retries, then fail (plus notification policy).
30 votes
- Don't see your idea?