run merb-gen without arguments to see generators available on your system.
Additional gems may provide their own generators.
--
MK
This has it's reasoning: in the end teams of developers end up keeping
database.yml ignored in SCM
because it's hard to use absolutely the same set up across different
machines. The most obvious example is
a socket file that is stored in different locations depending on how
you did install MySQL, PostgreSQL or whatever it is.
MacPorts use one path, Debian packages use some other, building from
source results in some 3rd location. So it's environment specific.
--
MK
Either merb-helpers is not loaded at all, or (for some very weird
reason) default form builder is not set.
--
MK
Both should not matter here. What is in your init file?
--
MK
If you cannot find require 'dependencies' in init.rb then yes, it's a
generated template issue.
--
MK
> Dick,
>
> I mentioned --orm switch at:
>
> http://groups.google.com/group/merb/browse_thread/thread/8cd0ea8cf6f43bd1#
Hi Arun
that's a separate issue; I'm saying that on JRuby,
you have to use 'merb-gen core' because 'merb-gen app' has no '--orm' option
(since it's supposed to be t 'quickstart' option).
The 'core' path is harder for new users (as it should be; that's the
'roll your own' option) ;
hence the workarounds you've described to get scaffolding working.
If merb-gen app took an --orm option, there'd be no need for JRuby users
to run 'merb-gen core' so early on in their Merb careers.
Not sure how hardcore is replacing a few characters on the command
line. If we bring --orm option
back to merb stack generator, that generator would not make any sense:
it would make it virtually
non different from the "core" generator.
merb-gen generators list mentions what every generator does.
--
MK
>> newbies trying out merb + jruby get forced down the 'hardcore'
>> path of 'merb-gen core'.
>
> Not sure how hardcore is replacing a few characters on the command
> line.
Sorry if I misunderstood, but I thought running 'merb-gen core' meant you
had to write the scaffolding code by hand, edit config/init.db to add
dependencies , etc.
> If we bring --orm option
> back to merb stack generator, that generator would not make any sense:
> it would make it virtually non different from the "core" generator.
Point taken, it was just a thought.
Correct, and it is intentional. Core generator lets you pick
components you want:
I have a few small applications that only use merb-core, sequel and
merb-messenger, all for
22 megs of ram.
--
MK