bcb36d9b6d
There are now 3 modes for deployment: next, stable, archive. We compute which mode (and other deployment properties) from the `TRAVIS_BRANCH` and the `STABLE_BRANCH`. If the TRAVIS_BRANCH is master we deploy as "next". Otherwise if the branch is the highest of its minor versions we deploy as "stable" if the `TRAVIS_BRANCH` matches the `STABLE_BRANCH` or else "archive". For "archive" deployments we compute the firebase project and deployment url based on the major version of the `TRAVIS_BRANCH`. As well as choosing where to deploy the build, we also use this to select the environment file for the AIO Angular app. This will enable the app to change its rendering and behaviour based on its mode. See #18287
20 lines
723 B
TypeScript
20 lines
723 B
TypeScript
// The file contents for the current environment will overwrite these during build.
|
|
// The build system defaults to the dev environment which uses `environment.ts`, but if you do
|
|
// `ng build --env=prod` then `environment.prod.ts` will be used instead.
|
|
// The list of which env maps to which file can be found in `angular-cli.json`.
|
|
|
|
|
|
// Reflect.metadata polyfill is only needed in the JIT/dev mode.
|
|
//
|
|
// In order to load these polyfills early enough (before app code), polyfill.ts imports this file to
|
|
// to change the order in the final bundle.
|
|
import 'core-js/es6/reflect';
|
|
import 'core-js/es7/reflect';
|
|
|
|
|
|
export const environment = {
|
|
gaId: 'UA-8594346-26', // Development id
|
|
production: false,
|
|
mode: 'stable'
|
|
};
|