Access env.var and options inside app

dr.dimitru · January 17, 2018, 2:29pm

Hello folks,

I was going to implement this feature request on ostrio:files package. But stuck with a question:

How to access next options and env.vars inside application at Server and Client?:

MOBILE_ROOT_URL
MOBILE_DDP_URL
--mobile-server argument

I’m sorry if this question is obvious, but for some reason, I cannot figure this out. I was 100% sure it will be placed into __meteor_runtime_config__, but it isn’t.

Thanks in advance.

kaufmae · January 19, 2018, 6:04am

Just guessing: I think the —mobile-server option is not really accessible in client code as it is used at compile time by cordova. After that it is the root url i guess. Maybe those env vars behave the same. The client code in the app connects to a localhost 127.* ip webserver once it is started and does not need to know these settings.

dr.dimitru · January 23, 2018, 9:07pm

Good guess, thank you.

I’m looking for reference or tested code sample.
Hopefully someone who are building Cordova app on daily basis could step-in.

kaufmae · January 23, 2018, 11:37pm

You should be able to get the mobile-server config on the server with process.env.MOBILE_ROOT_URL at startup and on the client with meteor_runtime_config.ROOT_URL in Meteor.isCordova mode.

github.com

meteor/meteor/blob/ac085d96fb79dfc03d28af8d4a3de50e99313ce4/tools/runners/run-app.js#L164


  self.onExit = null;
},


_computeEnvironment: function () {
  var self = this;
  var env = _.extend({}, process.env);


  env.PORT = self.port;
  env.ROOT_URL = self.rootUrl;
  env.MONGO_URL = self.mongoUrl;
  if (self.mobileServerUrl) {
    env.MOBILE_DDP_URL = self.mobileServerUrl;
    env.MOBILE_ROOT_URL = self.mobileServerUrl;
  }


  if (self.oplogUrl) {
    env.MONGO_OPLOG_URL = self.oplogUrl;
  }
  if (self.settings) {
    env.METEOR_SETTINGS = self.settings;
  } else {

github.com

meteor/meteor/blob/bdf80916879504d5b69745792984e8b92bfb474c/tools/cordova/builder.js#L431


    WebAppHashing.calculateClientHash(program.manifest, null, configDummy);
}


generateBootstrapPage(applicationPath, program, publicSettings) {
  const meteorRelease =
    release.current.isCheckout() ? "none" : release.current.name;


  const manifest = program.manifest;
  const autoupdateVersion = process.env.AUTOUPDATE_VERSION || program.version;


  const mobileServerUrl = this.options.mobileServerUrl;


  const runtimeConfig = {
    meteorRelease: meteorRelease,
    ROOT_URL: mobileServerUrl,
    // XXX propagate it from this.options?
    ROOT_URL_PATH_PREFIX: '',
    DDP_DEFAULT_CONNECTION_URL: mobileServerUrl,
    autoupdateVersionCordova: autoupdateVersion,
    appId: this.projectContext.appIdentifier,
    meteorEnv: {

github.com

meteor/meteor/blob/79b5ed8e6524ccbd573c1900188090ec13f81fb9/packages/webapp/webapp_server.js#L588


      process.exit(1);
    }
  });
};


WebAppInternals.generateBoilerplate = function () {
  // This boilerplate will be served to the mobile devices when used with
  // Meteor/Cordova for the Hot-Code Push and since the file will be served by
  // the device's server, it is important to set the DDP url to the actual
  // Meteor server accepting DDP connections and not the device's file server.
  var defaultOptionsForArch = {
    'web.cordova': {
      runtimeConfigOverrides: {
        // XXX We use absoluteUrl() here so that we serve https://
        // URLs to cordova clients if force-ssl is in use. If we were
        // to use __meteor_runtime_config__.ROOT_URL instead of
        // absoluteUrl(), then Cordova clients would immediately get a
        // HCP setting their DDP_DEFAULT_CONNECTION_URL to
        // http://example.meteor.com. This breaks the app, because
        // force-ssl doesn't serve CORS headers on 302
        // redirects. (Plus it's undesirable to have clients