Hi David,

On Fri, 2009-07-17 at 08:12 +0800, David Chua wrote:
> Hi Bill,
> 
> Thanks for the link.

You're welcome.

> I've looked through the source code but I couldn't find what I'm
> looking for. The app doesn't seem to be seeding data?

Depends on what you mean by 'seeding' I guess.  It's not using seed_fu.
But, if I understand (not having used it) what seed-fu does, it does
what Bala's User.create method does, just in a batch-type mode.  Bala's
UserObserver class takes care of the getting the aasm started and
kicking off the mailer functionality I thought you're looking for.
Seemed to me like an straight-forward marriage.  But maybe I
misunderstood.  If so, sorry for the noise.

Best regards,
Bill


> Warmest regards,
> David
> 
> On Fri, Jul 17, 2009 at 12:53 AM, bill walton <[email protected]>
> wrote:
>         
>         Hi David,
>         
>         On Thu, 2009-07-16 at 09:20 -0700, David Chua wrote:
>         > Hi all,
>         >
>         > Sorry for reviving a 6 day old e-mail, but I have a similar
>         question
>         > that I can't seem to figure out.
>         >
>         > I'm running restful_authentication with -aasm and I'm
>         looking to seed
>         > my user data such that an e-mail will be sent to the user
>         after
>         > creation to activate the account.
>         >
>         > Has anyone done something similar?
>         
>         
>         Check out Bala Paranj's simply-rich-authenticator mini app.
>         
>         http://code.google.com/p/simply-rich-authenticator
>         
>         HTH,
>         Bill
>         
>         
>         
>         
>         
> 
> 
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to