@peterlnguyen, I'm going to place this into Alpha 02 because it is somewhat related to the work you're doing with the interviewer. While it would be nice to include this in Alpha 02, it would be fine if this waited until Alpha 03.
Every service that is being deployed has a configuration. Currently that is stored in the manifest file, huxley.yaml, at the root of the application's repository.
These should instead be listed in the service's subdirectory of launch/. Specifically, we wish to store them in a file named config.yaml
This will require work on both how the interviewer responds to configuration entered during the mixin command and how the githook (the CoffeeScript file that gets placed with panda-hook) reads the configuration.
@peterlnguyen, I'm going to place this into Alpha 02 because it is somewhat related to the work you're doing with the interviewer. While it would be nice to include this in Alpha 02, it would be fine if this waited until Alpha 03.
Every service that is being deployed has a configuration. Currently that is stored in the manifest file,
huxley.yaml, at the root of the application's repository.These should instead be listed in the service's subdirectory of
launch/. Specifically, we wish to store them in a file namedconfig.yamlFor example:
This will require work on both how the interviewer responds to configuration entered during the mixin command and how the githook (the CoffeeScript file that gets placed with panda-hook) reads the configuration.