It's a great job they've done to "get it working" right and quickly, though the topic of production stability can be expected to stay warm unless a true "mod_ruby" lets us have our cake and eat it, too.
On Tue, Aug 19, 2008 at 8:20 AM, eric <[EMAIL PROTECTED]> wrote: > > What's strange is that it was working last night... > > > On Aug 19, 7:41 am, "Jesse Crockett" <[EMAIL PROTECTED]> wrote: > > The usual suspects could be factored out with any of the following > tasks.. > > > > rake install (reinstall) > > rake db:migrate VERSION=0 > > rake db:migrate > > delete cookies from browser (unrelated, but worth mentioning) > > > > I faced this error a few days ago, but I go "into the zone" and run a > whole > > bunch of destructive commands until the phoenix flies again. > > > > On Tue, Aug 19, 2008 at 7:10 AM, eric <[EMAIL PROTECTED]> wrote: > > > > > I just got this error, too: > > > OpenSSL::PKey::RSAError in SessionsController#create > > > > > Running the latest version of Insoshi (NOT on Heroku) > > > > > Any ideas? > > > > > On Jun 25, 6:01 am, Sacha Vimjavich <[EMAIL PROTECTED]> > > > wrote: > > > > Oh, found this: > > > > > > 1. Don't clear your cookies when you are on the login screen. > > > > OR > > > > 2. Don't use the default cookie session store. Rails by default uses > > > > cookies to store the sessions so when you essentially clear your > > > > cookies > > > > while you are the login screen it clears all the information about > the > > > > session and then thinks its a forgery attempt. > > > > > > But i am still getting the: > > > > > > OpenSSL::PKey::RSAErrorin SessionsController#create > > > > padding check failed > > > > > > Any patch to this: > > > > Gladly appreciated your help. > > > > > > On Jun 25, 6:54 pm, Sacha Vimjavich <[EMAIL PROTECTED] > > > > > > wrote: > > > > > > > Hi Long! > > > > > > > What could i do if i keep getting: > > > > > ActionController::InvalidAuthenticityToken in > > > > > SessionsController#create > > > > > > > ActionController::InvalidAuthenticityToken > > > > > > > ?? > > > > > Thanks! > > > > > > > On Jun 24, 9:35 am, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > > > > > > > > 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 -~----------~----~----~----~------~----~------~--~---
