This PR adds support for assigning custom names to templates installed with ore install. The idea is that you can name your repository something like vagrant_plugin_ore_template.git, but clone it into the directory ~/.ore/templates/vagrant_plugin. This way, mine will expose the options --vagrant-plugin and --no-vagrant-plugin rather than --vagrant-plugin-ore-template and --no-vagrant-plugin-ore-template.
I've added a nearly-bare git repository as a testing fixture in order to permit running ore install during tests without having to hit the network. If this is overkill, I am happy to replace the local repo with an external repo; perhaps one of the ruby-ore org's custom templates?
This PR adds support for assigning custom names to templates installed with
ore install. The idea is that you can name your repository something likevagrant_plugin_ore_template.git, but clone it into the directory~/.ore/templates/vagrant_plugin. This way,minewill expose the options--vagrant-pluginand--no-vagrant-pluginrather than--vagrant-plugin-ore-templateand--no-vagrant-plugin-ore-template.I've added a nearly-bare git repository as a testing fixture in order to permit running
ore installduring tests without having to hit the network. If this is overkill, I am happy to replace the local repo with an external repo; perhaps one of theruby-oreorg's custom templates?Thanks in advance for your consideration!