Working with their support guys. They've got some other apps that are also using ferret so hopefully we'll get a working solution put together.
Long On Mon, Jun 23, 2008 at 6:37 AM, Aaron <[EMAIL PROTECTED]> wrote: > > Any luck figuring out the details on the production configuration? If > i could get ferret to behave correctly I think it would work just fine > on Heroku. > > Aaron > > On Jun 19, 5:09 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > > This sounds like it's running in a clustered configuration. > > > > Check to see if you have any options for setting the number of mongrels > in > > production mode. (I haven't had a chance to get any of my app instances > > blessed on Heroku since I've been mainly trying to see the various ways I > > could load the Insoshi code using Git, tarball, etc.. This usually > involves > > destroying the app on a fairly regular basis...) > > > > On Thu, Jun 19, 2008 at 12:05 PM, Aaron <[EMAIL PROTECTED] > > > > wrote: > > > > > > > > > > > > > Hmm I have now noticed that I am getting a Ferret::FileNotFoundError > > > after a few minutes of using the site.. any ideas? > > > > > On Jun 18, 6:32 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > > > > If things are running as a single mongrel*, then you can comment out > the > > > > production runtime settings in ferret_server.yml so that it's not > > > expecting > > > > to communicate with a background process. > > > > > > This would be applicable to any hosted solution (not just Heroku) > where > > > you > > > > may not have access to start/stop background processes. > > > > > > *For multiple mongrels (cluster configuration), you do need to have a > > > > separate background process with ferret otherwise each mongrel will > > > assume > > > > it has control of files in the ferret index which leads to various > > > > file-not-found exceptions as one mongrel might erase/update/move a > file > > > that > > > > another one is trying to use. > > > > > > And thanks for posting a summary of steps to get running on Heroku! > > > > > > Long > > > > > > On Wed, Jun 18, 2008 at 2:51 PM, Aaron < > [EMAIL PROTECTED]> > > > > wrote: > > > > > > > Hey everyone I have been successful in getting Insoshi and Heroku > > > > > working together.. I am on one last stumbling block.. > > > > > > > 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. > > > > > > > Do I need to boot the ferret server? If so how? I am new to Rails > and > > > > > Ruby.. so any help would be great. > > > > > > > Thanks > > > > > > > Aaron > > > > > > -- > > > > Long Nguyen > > > > [EMAIL PROTECTED] > > > > -- > > Long Nguyen > > [EMAIL PROTECTED] > > > -- Long Nguyen [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" 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/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
