[DAEMON-178] Sync "appc ti config" with the "appc appcd config"
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Resolved |
| Resolution | Won't Do |
| Resolution Date | 2019-04-01T06:33:35.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | appcd |
| Labels | n/a |
| Reporter | Kondal Kolipaka |
| Assignee | Chris Barber |
| Created | 2017-11-22T06:24:41.000+0000 |
| Updated | 2019-04-01T06:33:36.000+0000 |
Description
How and when do we sync
appc ti config settings to appc appcd config - so that when studio is working with Appc Daemon it can only look for appc appcd config
Since everybody is trained to work with appc ti config and they might configure android.sdkPath, sdk.selected,etc., and expect they will be picked up directly in the studio
Any thoughts around it?
The Titanium CLI is automatically imported one time during the daemon startup. Once it has been imported, it will never try to import it again. The Appc Daemon encourages plugins to namespace their config settings which means they can coexist and share settings among plugins. If and when the Appc CLI plugin becomes a reality, it will replace the Titanium CLI along with its config. On a side note, you can control the Appc Daemon's config via the
/appcd/configservice endpoint. You can also subscribe to config changes.