wycats / merb-more
- Source
- Commits
- Network (33)
- Issues (0)
- Downloads (9)
- Wiki (1)
- Graphs
-
Tree:
bef3a6f
commit bef3a6fc47a0c7fe83be54f69895952e175abc16
tree 13b5fce7a58f428cac0f174db1f14261830773ce
parent 462369c5d8f244873aef1352a24410c20ecf0321
tree 13b5fce7a58f428cac0f174db1f14261830773ce
parent 462369c5d8f244873aef1352a24410c20ecf0321
merb-more / merb-gen
merb-gen/README
==== merb-gen
merb-gen is a part of the Merb More package. It provides application, plugin, and component
generators for Merb.
==== Usage
To generate directory structure for a new merb app, run merb-gen app <app-name>.
For instance, <tt>merb-gen app foo</tt> would create a new foo merb app inside of the foo directory.
Use <tt>--flat</tt> to generate a flattened application (very simple directory structure)
and <tt>--very-flat</tt> to generate a single file application.
To generate a new merb plugin, run merb-gen plugin <plugin_name>.
To see what generators are available, run merb-gen generators.
==== Custom generators
There are two ways of adding generators, depending on how the generators are intended to be used. The first way is by
adding adding the generator via Merb.add_generators, and specifying the location of any generators.
Merb.add_generators File.join(File.dirname(__FILES__), 'generators', 'my_generator.rb')
This method has some advantages:
- it allows you to load generators only when your plugin is required in the application
- it allows you to load generators from inside the application itself
However, it also has a disadvantage: it is impossible this way to add generators whether the plugin is loaded or not,
just by virtue of the gem being installed. This is where the second way comes in: A 'Generators' file is added to the
root of the project (like a Rakefile), it should look something like this:
scope "merb-gen" do
Merb.add_generators File.join(File.dirname(__FILES__), 'generators', 'my_generator.rb')
end
