[ALOY-601] Use env variables from config.json for distributed builds
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | n/a |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2013-04-05T12:10:43.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 07 |
| Components | n/a |
| Labels | alloy, alloy-cli, cli |
| Reporter | Pedro Enrique |
| Assignee | Tony Lukasavage |
| Created | 2013-03-19T18:56:13.000+0000 |
| Updated | 2014-01-28T23:55:23.000+0000 |
Description
When building an app for distribution purposes (in my case, ad-hoc distribution of an iPhone app to send to beta testers), I would like the build to use development or test environment variables (env:development, env:test) set in config.json instead of production variables (env:production). This would allow me to create a build that points to development backend services and test data and would be perfect for testing purposes.
It would avoid the pitfalls of manually changing paths, datasources, etc before build and changing them back when ready for production.
Perhaps this feature could exist as a flag or a setting in build config.
original discussion here:
http://developer.appcelerator.com/question/149729/deploy-ios-ad-hoc-using-dev-environment-variables-in-configjson#answer-258914
You'll have to do this from the command line, as there's no option for it in TiStudio, but you can define an explicit "deploytype" for your alloy compile process. For example, if I want to compile alloy for ios and a "development" environment regardless of what the CLI thinks, I would do this:
Notice that there's no space between the comma, it's all one string after --config