The uninitialized constant Crypto::Key::Base64  error doesn't seem to
be addressed in any of the tutorials I have found.. even the one that
was up and running for people to see does not allow new signup's
because of this error.

Any ideas?

On Jun 14, 1:51 pm, SimianLogic <[EMAIL PROTECTED]> wrote:
> I did a post on it when it first came out.  They've fixed a couple of
> the issues, but if you work through it problem by problem you can get
> it going fairly well.
>
> http://simianlogic3d.com/blog/2008/04/30/insoshi-meet-heroku/
>
> On Jun 13, 10:57 pm, Aaron <[EMAIL PROTECTED]> wrote:
>
> > Has anyone got Insoshi up and running on Heroku? I get the following
> > error when trying to rake after the tar upload.
>
> > rake aborted!
> > uninitialized constant Crypto::Key::Base64
>
> > (See full trace by running task with --trace)
> > (in /mnt/home/userapps/20801)
> > == 13 AddAdmin: migrating ====================
> > -- add_column(:people, :admin, :boolean,
> > {:default=>false, :null=>false})
> >    -> 0.0069s
> > -- add_column(:people, :deactivated, :boolean,
> > {:default=>false, :null=>false})
> >    -> 0.0049s
>
> > If anyone has this up and running I would love to know what steps to
> > go through. I thought I found a site that was working at:
> > cmich.heroku.com
>
> > but when I signed up to ask the developer how he did it.. I got the
> > following error:
>
> > uninitialized constant Crypto::Key::Base64
>
> > So does anyone know how to get this working? I am considering creating
> > my own using my railsspace book with the rails 2.0 fixes.. but it
> > would be faster just to customize Insoshi if I can get it working..
>
> > Thanks.
>
> > Aaron
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Heroku" 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/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to