METEOR_RELEASE env variable?


#1

Does anybody know of an environment variable where we can specify the meteor release? We’d really like to do something along the lines of

METEOR_RELEASE=clinical:METEOR@1.1.3-rc4 meteor

instead of

meteor --release clinical:METEOR@1.1.3-rc4

Unfortunately, finding documentation on things like environment variables is difficult. I went through the entire Meteor codebase back around ~1.0.3, and came up with the following list of environment variables. I’m hoping I missed something or something new was introduced since I last compiled this list.

PORT:                                  not specified
MONGO_URL:                             not specified
ROOT_URL:                              not specified
OPLOG_URL:                             not specified
MONGO_OPLOG_URL:                       not specified
METEOR_ENV:                            not specified
NODE_ENV:                              not specified
NODE_OPTIONS:                          not specified
DISABLE_WEBSOCKETS:                    not specified
MAIL_URL:                              not specified
DDP_DEFAULT_CONNECTION_URL:            not specified
HTTP_PROXY:                            not specified
HTTPS_PROXY:                           not specified
METEOR_OFFLINE_CATALOG:                not specified
METEOR_PROFILE:                        not specified
METEOR_DEBUG_BUILD:                    not specified
TINYTEST_FILTER:                       not specified
MOBILE_ROOT_URL:                       not specified
NODE_DEBUG:                            not specified
BIND_IP:                               not specified
PACKAGE_DIRS:                          not specified
DEBUG:                                 not specified

METEOR_PRINT_CONSTRAINT_SOLVER_INPUT:  not specified
METEOR_CATALOG_COMPRESS_RPCS:          not specified
METEOR_MINIFY_LEGACY:                  not specified
METEOR_DEBUG_SQL:                      not specified
METEOR_WAREHOUSE_DIR:                  not specified
AUTOUPDATE_VERSION:                    not specified
USE_GLOBAL_ADK:                        not specified
METEOR_AVD:                            not specified
DEFAULT_AVD_NAME:                      not specified
METEOR_BUILD_FARM_URL:                 not specified
METEOR_PACKAGE_SERVER_URL:             not specified
METEOR_PACKAGE_STATS_SERVER_URL:       not specified
DEPLOY_HOSTNAME:                       not specified
METEOR_SESSION_FILE:                   not specified
METEOR_PROGRESS_DEBUG:                 not specified
METEOR_PRETTY_OUTPUT:                  not specified
APP_ID:                                not specified
AUTOUPDATE_VERSION:                    not specified
CONSTRAINT_SOLVER_BENCHMARK:           not specified
DDP_DEFAULT_CONNECTION_URL:            not specified
SERVER_WEBSOCKET_COMPRESSION:          not specified
USE_JSESSIONID:                        not specified
METEOR_PKG_SPIDERABLE_PHANTOMJS_ARGS:  not specified
WRITE_RUNNER_JS:                       not specified
TINYTEST_FILTER:                       not specified
METEOR_PARENT_PID:                     not specified
METEOR_TOOL_PATH:                      not specified
RUN_ONCE_OUTCOME:                      not specified
TREE_HASH_DEBUG:                       not specified
METEOR_DEBUG_SPRINGBOARD:              not specified
METEOR_TEST_FAIL_RELEASE_DOWNLOAD:     not specified
METEOR_CATALOG_COMPRESS_RPCS:          not specified
METEOR_TEST_LATEST_RELEASE:            not specified
METEOR_WATCH_POLLING_INTERVAL_MS:      not specified
EMACS:                                 not specified
METEOR_PACKAGE_STATS_TEST_OUTPUT:      not specified
METEOR_TEST_TMP:                       not specified
```

Any ideas on how we might be able to specify meteor track via environment variable?  The ``--release`` flag is good; but we've already had a few times where things have gotten borked because we forgot it.  Would be nice to be able to tell the shell environment 'yeah, seriously; use this release for *everything*, until we tell you otherwise'.

#2

Hi @awatson1978

In case that you do not found what looking for just use linux / bash

 METEOR_RELEASE=clinical:METEOR@1.1.3-rc4 meteor --release $METEOR_RELEASE

or create an alias

alias meteor='meteor --release $METEOR_RELEASE'

and run

METEOR_RELEASE=clinical:METEOR@1.1.3-rc4 meteor

Cheers
Tom