I have a constant file
export class constants {
public static get API_ENDPOINT(): string { return \'https://dvelopment-server/\'; }
}
I would just like to add put some more light into the answer provided by @Cartucho. He is right about the steps required to setup a personalized environment for your angular 2 apps. I would also like to second the opinion that the article at Guide to Build the app in different environments
But the given article misses out on an important step. Steps to set up a personalized environment are as follows: 1) Create a new file called environment.YourEnvName.ts in the environments folder in the project. 2) Add the Environment description in the "environments" object in the angular-cli.json file.
"environments": {
"source": "environments/environment.ts",
"prod": "environments/environment.prod.ts",
"dev": "environments/environment.dev.ts",
"qa": "environments/environment.qa.ts",
"YourEnvName": "environments/environment.YourEnvName.ts"
}
3) Once you have made these changes you can build the app for your new environment using the following command.
ng build --environment=YourEnvName or
ng serve --environment=YourEnvName
Hope this post is helpful to any new Angular 2 developer.
export class endPointconfig {
public static getEnvironmentVariable() {
let origin = location.origin;
let path = location.href.split('/')[3];
let value = origin +'/'+ path + '/api/';`enter code here`
return value;
}
}
I hope it helps.
First, create development.ts, staging.ts, production.ts configuration files. Second, in your index.pug, import the environment file in the following way:
SystemJS.import("#{settings.env}").then(function(env) {
System.import("app").catch(console.error.bind(console));
} // Promise.all also works!
Remember that in nodeJS/Pug/Jade settings.env contains the NODE_ENV value.
And finally, your system.config.ts map should have the following lines:
"development": "myUrl/configs/development.js",
"staging": "myUrl/configs/staging.js",
"production": "myUrl/configs/production.js",
Short answer: use Angular CLI. It is in beta stage but works really well and it's recommended by the Angular Team for starting new projects. With this tool you can configure different environments. At build time, the src/client/app/environment.ts
will be replaced by either config/environment.dev.ts
or config/environment.prod.ts
, depending on the current CLI environment.
Environment defaults to dev
, but you can generate a production build via the -prod
flag in either ng build -prod
or ng serve -prod
. Given that this is a new feature, it can be a bit confuse, so look at this great guide for additional info about how to set up Angular Environments using CLI.
Hope this helps.
I have solved the issue by adding a class method
export class config {
public static getEnvironmentVariable(value) {
var environment:string;
var data = {};
environment = window.location.hostname;
switch (environment) {
case'localhost':
data = {
endPoint: 'https://dev.xxxxx.com/'
};
break;
case 'uat.server.com':
data = {
endPoint: 'https://uat.xxxxx.com/'
};
break;
default:
data = {
endPoint: 'https://dev.xxxx.com/'
};
}
return data[value];
}
}
In my service
private _loginUrl = config.getEnvironmentVariable('endPoint')+'api/v1/login;