diff --git a/examples/functions/functions_tester/test/integration/materializeTotalSales.test.js b/examples/functions/functions_tester/test/integration/materializeTotalSales.test.js index 8511181fd..55a7d8eeb 100644 --- a/examples/functions/functions_tester/test/integration/materializeTotalSales.test.js +++ b/examples/functions/functions_tester/test/integration/materializeTotalSales.test.js @@ -1,5 +1,5 @@ // :snippet-start: materialize-total-sales-test -const { app_id } = require("../../realm_config.json"); +const { app_id } = require("../../root_config.json"); const Realm = require("realm"); const { BSON } = require("realm"); diff --git a/source/apps/copy-app-copy-config-files.rst b/source/apps/copy-app-copy-config-files.rst index c5e966b58..6e50fd9d8 100644 --- a/source/apps/copy-app-copy-config-files.rst +++ b/source/apps/copy-app-copy-config-files.rst @@ -1,6 +1,6 @@ Copy all configuration files from your original App, except for -``realm_config.json``, to the new App's configuration directory. You -should use the new App's ``realm_config.json`` and overwrite any other +``root_config.json``, to the new App's configuration directory. You +should use the new App's ``root_config.json`` and overwrite any other configuration files. .. example:: diff --git a/source/apps/environment.txt b/source/apps/environment.txt index c7502f017..13a0b50a3 100644 --- a/source/apps/environment.txt +++ b/source/apps/environment.txt @@ -215,10 +215,10 @@ Procedure Your app always runs in a specific environment, which affects the value of all environment values. You can specify the current environment for your app in - ``realm_config.json``: + ``root_config.json``: .. code-block:: json - :caption: realm_config.json + :caption: root_config.json { ..., diff --git a/source/examples/generated/functions/materializeTotalSales.test.snippet.materialize-total-sales-test.js b/source/examples/generated/functions/materializeTotalSales.test.snippet.materialize-total-sales-test.js index a901105be..563977a48 100644 --- a/source/examples/generated/functions/materializeTotalSales.test.snippet.materialize-total-sales-test.js +++ b/source/examples/generated/functions/materializeTotalSales.test.snippet.materialize-total-sales-test.js @@ -1,4 +1,4 @@ -const { app_id } = require("../../realm_config.json"); +const { app_id } = require("../../root_config.json"); const Realm = require("realm"); const { BSON } = require("realm"); diff --git a/source/reference/config.txt b/source/reference/config.txt index 5b2841a9d..86f88b5f6 100644 --- a/source/reference/config.txt +++ b/source/reference/config.txt @@ -47,7 +47,7 @@ using structured JSON configuration and JavaScript source code files. You can include arbitrarily named files in your realm app config, with a few exceptions. The following filenames are used to define and configure components in your App: - ``stitch.json``, ``config.json``, ``realm_config.json``, and ``app_config.json``. + ``stitch.json``, ``config.json``, ``root_config.json``, and ``app_config.json``. Files with these names must conform to a specific schema for their component type. Using these file names when the file's content fails to conform to that schema throws an error when you import the app using the CLI. diff --git a/source/security/network.txt b/source/security/network.txt index 232d62001..59a3f3cfc 100644 --- a/source/security/network.txt +++ b/source/security/network.txt @@ -225,7 +225,7 @@ Allowed Request Origins ----------------------- You can define this :ref:`configuration option ` in the -app-level ``realm_config.json`` file. This field accepts an array of +app-level ``root_config.json`` file. This field accepts an array of URLs that incoming requests may originate from. If you define any allowed request origins, then App Services blocks any incoming request from an origin that is not listed. diff --git a/source/tutorial/react-native.txt b/source/tutorial/react-native.txt index 2e44d1654..86d7b2623 100644 --- a/source/tutorial/react-native.txt +++ b/source/tutorial/react-native.txt @@ -251,8 +251,8 @@ Atlas App Services App ~~~~~~~~~~~~~~~~~~~~~~ The template app includes a fully configured App Services App in the -``backend`` directory. It has a unique ``app_id`` value in -``realm_config.json`` that client applications use to connect. +``backend`` directory. It has a unique ``appId`` value in +``atlasConfig.json`` that client applications use to connect. It also includes the following pre-defined configurations: