You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 24, 2021. It is now read-only.
@@ -119,3 +101,62 @@ We're reading the contents of index.html using the [Assets](https://docs.meteor.
119
101
We're using the [connect-route](https://www.npmjs.com/package/connect-route) NPM package to simplify WebApp route processing. But you can use any package you want to understand what is being requested.
120
102
121
103
And finally, if you decide to use this technique you'll want to make sure you understand how conflicting client side routing will affect user experience.
104
+
105
+
### Dynamic Runtime Configuration
106
+
107
+
In some cases it is valuable to be able to control the __meteor_runtime_config__ variable that initializes Meteor at runtime.
108
+
109
+
#### Example
110
+
There are occasions when a single Meteor server would like to serve multiple cordova applications that each have a unique `ROOT_URL`. But there are 2 problems:
111
+
1. The Meteor server can only be configured to serve a single `ROOT_URL`.
112
+
2. The `cordova` applications are build time configured with a specific `ROOT_URL`.
113
+
114
+
These 2 conditions break `autoupdate` for the cordova applications. `cordova-plugin-meteor-webapp` will fail the update if the `ROOT_URL` from the server does not match the build time configured `ROOT_URL` of the cordova application.
115
+
116
+
To remedy this problem `webapp` has a hook for dynamically configuring `__meteor_runtime_config__` on the server.
0 commit comments