Environment variable overwritten

cf-meteor-buildpack/bin/release

extract_root_url()

Custom domains are ignored. If I set an user variable with ROOT_URL, it is ignored and only the VCAP application is taken. While this is nice with the standard settings it causes problems if you want to overwrite this with a custom domain on purpose. (using bluemix, not sure if this is a common problem)

It would be nice to have a check if there is an existing environment variable and only set a new one if there is not.

[djules75]

I have the same problem. I'm using a custom domain and the ROOT_URL environment variable that I set through 'cf env' is overridden by the standard settings from the buildpack. Any solution for this?

[djules75]

Just implemented a work around using a BLUEMIX_ROOT_URL env variable, then, in my init script on server side:

if (process.env.BLUEMIX_ROOT_URL) {
  __meteor_runtime_config__.ROOT_URL = process.env.BLUEMIX_ROOT_URL;
  Meteor.absoluteUrl.defaultOptions.rootUrl = process.env.BLUEMIX_ROOT_URL;
}