I did a post on it about a month ago, but I haven't kept it up to date with the new releases of Insoshi.
http://simianlogic3d.com/blog/2008/04/30/insoshi-meet-heroku/ The span problem (if you're talking about what I think you're talking about) can be fixed through use of the heroku.yml file in your config directory-- just put the two necessary variables in: toolbar_collaborators: false toolbar_public: false -Will On Jun 2, 2:32 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > I've been doing some initial testing of Insoshi on Heroku. I'm currently > testing various methods to get the code up to an app instance (nothing > exciting to report yet, just really seeing what can be done through their > gem and Git especially in trying to get the latest updates). > > A couple of things that you might need to do: > > 1. Heroku inserts span tags into the HTML. There's an issue with the span > that gets inserted after the body tag that leads to broken HTML (and a blank > browser page). You will need to remove/comment out the class attribute for > the body tag in app/views/layouts/application.html.erb for now. (I'll send > the issue over to Heroku support.) > > 2. The incompatibility with PostgreSQL is a custom SQL statement for finding > common connections using an inner join. There's some characters (a backtick > quote) that it doesn't like and some additional columns that the GROUP BY > wants. I've been able to make those changes so it won't throw the exception > but haven't had a chance to verify it's behavior and what effect it has > under MySQL or SQLite. Here's the updated statement: > > 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) > > As I've said, it's enough to get the exception from showing but I'm not > guaranteeing anything else just yet. When we have an actual fix, it'll be > in our Git repository. > > If anyone else has been trying to get Insoshi up and going on Heroku, let me > know and I'll collect up the issues and tips to document and pass along. > > Long > > > > On Mon, Jun 2, 2008 at 12:09 PM, Ming <[EMAIL PROTECTED]> wrote: > > > Thanks, Brian. The importiing itself went well for me too. The problem > > only showed up when I tried the application on HeroKu. I will check > > the links you provided. > > > On Jun 2, 8:35 am, "B. Brian" <[EMAIL PROTECTED]> wrote: > > > I imported everything to Heroku successfully without any problem (but > > > it took a long time to finish):http://bwang.heroku.com > > > > But when trying the application, everything is ok exception some > > > database compatible issues. More details can be found from following > > > links: > >http://insoshi.lighthouseapp.com/projects/9331/tickets/75-postgresql-.... > > .. > > > > B. Brian > > > > On Jun 2, 3:17 am, Ming <[EMAIL PROTECTED]> wrote: > > > > > Anybody has imported Inshoshi successfully to HeroKu.com? > > > > I got many errors when trying to run Inshoshi on Heroku. Is there > > > > known compatibility issue? > > > > Thanks!- Hide quoted text - > > > > - Show quoted text - > > -- > 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 -~----------~----~----~----~------~----~------~--~---
