Ok the Crypto::Key::Base64 makes sense to me now because when a new
person object is created as an admin the application is trying to use
SSL. Because my app was unblessed that error would come up when the
migration created the default user. So the way to get around this is
to create your app, get it blessed, THEN run the migrations.

It does have to be blessed though because you can not log in as an
admin without the SSL, which only works on blessed apps.

So what I did to get my install working is this:

-upload tar ball through the settings tab:
-get app blessed
-run rake db:migrate
-run rake install
-disable the heroku toolbar by creating the following file named
heroku.yml in your config directory

    toolbar_collaborators: false
    toolbar_public: false

Then you need to replace the SQL that is not compatible with
PostgreSQL in the persons model.

The code that does not work looks like this:

sql = %(SELECT connections.*, COUNT(contact_id) FROM `connections`
WHERE ((person_id = ? OR person_id = ?)
AND status=?)
GROUP BY contact_id
HAVING count(contact_id) = 2)

Here is the workaround

sql = %(SELECT connections.*, COUNT(contact_id) FROM connections
         INNER
JOIN people contact ON connections.contact_id = contact.id
            WHERE ((person_id = ? OR person_id = ?)
                   AND status = ? AND
                   contact.deactivated = ? AND
                   (contact.email_verified IS NULL
                    OR contact.email_verified = ?))
            GROUP BY connections.id, person_id, contact_id, status,
accepted_at,
                     connections.created_at, connections.updated_at
            HAVING count(contact_id) = 2)

At this point you should have an app that works! The next issue you
will run into is Acts_as_ferret. When you put the application into
production instead of development you will start getting errors with
acts_as_ferret. There is a ferret_server.yml file in the config
directory with the following settings:

production:
  host: localhost
  port: 9010
  pid_file: log/ferret.pid
  log_file: log/ferret_server.log
  log_level: warn

THis is where I am stuck does anyone know how to set this file up? I
have Insoshi running in every other way I can think of accept this
last stumbling block.

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