merb Google Group

merb-1.1.0.pre - uninitialized constant Merb::Generators::ControllerGenerator (NameError)

2010-01-01T02:19:56Z

I've installed merb 1.1.0.pre on my production linux server and am
getting different behavior than on my OS X dev machine.
Running merb-gen as follows shows the problem.
mhd@us1:~$ merb-gen app merb_test
/home/mhd/ruby-191-p243/lib/ru by/gems/1.9.1/gems/merb-haml-1 .1.0.pre/
lib/generators/controller.rb:1 :in `<top (required)>': uninitialized

Re: Merb 1.0.15: run_later seems broken w/ clusters

2010-01-01T01:26:22Z

So on 1.0.15, I added some logging regarding run_later, initializing a
worker, and entering the work loop..
I get:
initializing! [82326, false, 0]
in worker! [82326, false, 0]
QUEUEING! [82327, true, 0]
and nothing else..
where 82326 is the PID of the spawner, 82327 is the PID of one of the
merb workers, the boolean is Merb::Worker.started?, and the number is

Merb 1.0.15: run_later seems broken w/ clusters

2010-01-01T00:09:30Z

run_later is working just fine in bin/merb -i or bin/merb, but no
longer seems to be working with the -c parameter (clustering).
The diffs btwn 1.0.12 and 1.0.15 are very small.. looks like the
worker starting was moved a little bit.. about to dive in more..
Has anyone been able to get run_later working on Merb 1.0.15 w/

Re: [merb] Re: Framework choice for a new app

2009-12-31T21:22:55Z

We just started a new project at work with Merb and have been very happy.
It's not as well documented as Rails, and while that does present some
initial challenges onboarding new people, keeping the more junior people
self-sufficient and understanding how certain features work, the benefits
for us of Merb far outweigh the initial headaches.

Re: [merb] create models from within thor tasks

2009-12-31T15:57:59Z

Hi,
I don't use thor but I store tasks in lib/tasks/custom.rake
for instance and they are just normal rake tasks
example:
task :add_topic_shit => :merb_env do
Topic.all.each do |topic|
tagz = topic.tags.collect do |tag| tag.title end
topic.keywords = tagz.join(", ")
topic.save
end
end

create models from within thor tasks

2009-12-30T22:02:35Z

how do you include merb in thor tasks? In rails rake tasks we use
something like
task :import_assets => :environment do
which makes it possible to load models inside tasks, but how is this
done using thor and merb?
desc 'booh', 'test datamapper'
def booh
Location.new
end
the line above gives me something like:

Re: Framework choice for a new app

2009-12-30T17:50:24Z

Martin,
Which will be easier to port to Rails3? If you want ActiveRecord, I
guess rails would be more straightforward port. Without ActiveRecord,
I don't think it matters.
If you want very simple, sinatra is nice. I stuck with merb for my
new app simply because despite sinatra's simplicity, I had many

Re: Framework choice for a new app

2009-12-30T17:41:14Z

This would be a great opportunity for Yehuda to jump in and give an
update on where things are up to on Rails 3, with some
characterization of how Rails 3 and Merb 1.1 will be related in terms
of architecture, api and performance and some assessment of when it
will make sense for merb apps to be migrated to the new platform. At

Framework choice for a new app

2009-12-30T10:14:57Z

Hello,
I'm going to start development of a new app and I'm wondering which
way to go on the framework choice.
I was leaning towards merb but since merb and rails are merging I'm
unsure.
What I'm mostly interested in is which of the frameworks is more
future "safe", which will be easier to port/upgrade to rails3?

Re: git commit id from merb gem build

2009-12-30T17:09:06Z

Mark, Martin, thanks for the replies.
Here's what I've discovered...hope this helps others:
1 - ruby-191-p376 does not work with merb 1.1.0.pre. From another
thread, it seems this is a problem with methopara.
2 - ruby-191-p243 seems to work well.
3 - You cannot have merb gems 1.1 installed along with merb 1.1.0.pre

Re: [merb] Re: git commit id from merb gem build

2009-12-30T15:17:53Z

Sorry, but since prerelease gems haven't always been possible, there
was no way to avoid switching from 1.1 to 1.1.0.pre at some time, if
we want the comfort of having prerelease gems. I'd suggest you remove
the old 1.1 gems from your machine(s). 1.1.0.pre (master branch) is
considered to be the most stable version. Also, to avoid problems with

Re: git commit id from merb gem build

2009-12-30T08:38:41Z

Jon,
According to gemcutter - [link]
, the 1.1.0.pre release was made on November 17, so I suppose the
latest from github on that date would be a fair guess -
[link] .
That said. I installed the HEAD version from github just yesterday,

Re: [merb] unsuscribe

2009-12-29T23:24:06Z

On Tue, Dec 29, 2009 at 10:53 PM, Cristian Malinescu
Think the problem is someone typing merb+unsuscribe@googlegroups.c om
instead of merb+unsubscribe@googlegroups. com.

Re: [merb] unsuscribe

2009-12-29T21:53:23Z

sorry, what's this?!

unsuscribe

2009-12-29T18:10:06Z