Closed adam-paterson closed 10 years ago
Thanks for pull request. Can you give me an example for the new config?
n98-magerun can load configs on system, user and project scope. Only user config is prefixed with a dot. All other configs name is "n98-magerun.yaml" without a dot as prefix.
The config file hasn't changed, my change just creates a .n98-magerun.yaml file in the install dir based on a local file specified in Vagrant.
The example below, won't show much. during a the provisioning of my Vagrant box it takes a copy of my local magerun config and creates the file on the vm.
# n98-magerun install
class { 'n98magerun':
config_file => '/vagrant/puppet/files/.n98-magerun.yaml'
}
I'm not sure if this is out of scope, but we use n98-magerun in our Magento skeleton with a custom private repositories for EE.
Adding this to my fork allows me to specify a custom config file in my puppet manifest and add it to the install dir.