Re: compass config logic question
>From the looks of it, Heroku just take quite a while to compile the stylesheets. Things seem to be working now after I got from breakfast. Sorry for the noise! Bram On May 17, 8:56 am, webdevotion wrote: > Hello > > I have a config logic question related to Compass. > After following the Heroku documentation I also wanted to be able to > generate the stylesheets on my local dev machine. > > My solution was to implement some logic in the config and initializer > like this:https://gist.github.com/976056 > > But it only works when I leave of the if statements. > ( question: is environment != 'production' in production mode? ) > > environment = Compass::AppIntegration::Rails.env > if environment == 'production' > ... > else > ... > end > > My conclusions: > - core compass code logic works > - only problem is the if statement ( production vs development > machine ) > - when printing Compass::AppIntegration::Rails.env I get 'production' > on Heroku > > Thanks for your insights! > Bram -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
compass config logic question
Hello I have a config logic question related to Compass. After following the Heroku documentation I also wanted to be able to generate the stylesheets on my local dev machine. My solution was to implement some logic in the config and initializer like this: https://gist.github.com/976056 But it only works when I leave of the if statements. ( question: is environment != 'production' in production mode? ) environment = Compass::AppIntegration::Rails.env if environment == 'production' ... else ... end My conclusions: - core compass code logic works - only problem is the if statement ( production vs development machine ) - when printing Compass::AppIntegration::Rails.env I get 'production' on Heroku Thanks for your insights! Bram -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: undefined method `reset_javascript_include_default' for ActionView::Helpers::AssetTagHelper:Module
updated bundler to the v1 beta which seems to solve some of the issues but now experiencing this: http://github.com/carlhuda/bundler/issues#issue/419 On Jul 2, 10:17 am, webdevotion wrote: > Hello > > I've got a new Rails 3 app, which works locally. > But once deployed to Heroku I get: > > "An error happened during the initialization of your app. This may be > due to a typo, wrong number of arguments, or calling a function that > doesn’t exists. Check the stack trace below for specific details. > Make sure the app is working locally in production mode, by running it > with RAILS_ENV (for Rails apps) or RACK_ENV (for Sinatra or other rack > apps) set to production. e.g. RAILS_ENV=production script/server." > > and in the terminal I get: > > heroku rake db:migrate > rake aborted! > undefined method `reset_javascript_include_default' for > ActionView::Helpers::AssetTagHelper:Module > > I'm on the bamboo-ree-1.8.7 stack. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
undefined method `reset_javascript_include_default' for ActionView::Helpers::AssetTagHelper:Module
Hello I've got a new Rails 3 app, which works locally. But once deployed to Heroku I get: "An error happened during the initialization of your app. This may be due to a typo, wrong number of arguments, or calling a function that doesn’t exists. Check the stack trace below for specific details. Make sure the app is working locally in production mode, by running it with RAILS_ENV (for Rails apps) or RACK_ENV (for Sinatra or other rack apps) set to production. e.g. RAILS_ENV=production script/server." and in the terminal I get: heroku rake db:migrate rake aborted! undefined method `reset_javascript_include_default' for ActionView::Helpers::AssetTagHelper:Module I'm on the bamboo-ree-1.8.7 stack. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Project.where(:status => true)
Thanks guys for your time. The problem was that status was defined as text in the migration file. * ouch * On Jun 16, 3:46 pm, webdevotion wrote: > Hey > > We have a problem with our Projects controller. > Where we want to select all the projects with status set to true we > use: > > p = Project.where(:status => true) > > It works locally, but it doesn't work on the Heroku instance. > > Does work, but not agnostic > p = Project.where(:status => '1') > > What's the best practice to solve this ( little ) problem? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Project.where(:status => true)
Hey Steve, This is the output from your suggested snippet: heroku console Ruby console for weekendr.heroku.com >> p = Project.where(["status = ?", true]) => [] >> On Jun 16, 4:22 pm, Steve Smith wrote: > Looks like Arel might not be escaping the true correctly which is strange. > How about > > p = Project.where(["status = ?", true]) > > Does that do the same thing? > Steve > > On 16 Jun 2010, at 14:46, webdevotion wrote: > > > > > Hey > > > We have a problem with our Projects controller. > > Where we want to select all the projects with status set to true we > > use: > > > p = Project.where(:status => true) > > > It works locally, but it doesn't work on the Heroku instance. > > > Does work, but not agnostic > > p = Project.where(:status => '1') > > > What's the best practice to solve this ( little ) problem? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Project.where(:status => true)
They said something about problems with casting a boolean to an
integer or something along those lines.
The problem is / was that the postrgresql db from heroku doesn't like
the native ruby boolean value used
in our projects#index action.
On Jun 16, 4:05 pm, Hemal Kuntawala wrote:
> Sounds like a db modelling issue. What do the heroku logs say? ('heroku
> logs')
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: Project.where(:status => true)
> Are you running postgresql locally? no, sqlite for local development machines -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Project.where(:status => true)
Hey We have a problem with our Projects controller. Where we want to select all the projects with status set to true we use: p = Project.where(:status => true) It works locally, but it doesn't work on the Heroku instance. Does work, but not agnostic p = Project.where(:status => '1') What's the best practice to solve this ( little ) problem? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Bundler 0.9.26
it's working fine now On Jun 14, 11:37 pm, Pedro Belo wrote: > Hey guys, > > We will be upgrading Bundler to 0.9.26 tomorrow. > > On a side note, we've been studying alternatives to this process so > you're not blocked on us whenever Rails bumps the Bundler version > dependency. We are well aware of this issue :) > > Thanks, > Pedro -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Bundler 0.9.26
Thanks! On Jun 14, 11:37 pm, Pedro Belo wrote: > Hey guys, > > We will be upgrading Bundler to 0.9.26 tomorrow. > > On a side note, we've been studying alternatives to this process so > you're not blocked on us whenever Rails bumps the Bundler version > dependency. We are well aware of this issue :) > > Thanks, > Pedro -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: rails-3.0.0.beta4 on bamboo-ree-1.8.7?
Good news! Looking forward to it! On Jun 11, 4:43 am, Pedro Belo wrote: > Hey guys! > > Thanks for reporting. We're aware we need to update Bundler - we'll > roll that out asap! > > On Thu, Jun 10, 2010 at 7:37 PM, Chris Hanks > > > > wrote: > > I'm anxious for Bundler 0.9.26 also! > > > On Jun 9, 3:31 am, Ariejan de Vroom wrote: > >> Hey, > > >> I'm running into a Bundler/Rails issue when trying to deploy a Rails > >> 3.0.0.beta4 app to the bamboo-ree-.1.8.7 stack. Rails 3b4 need bundler > >> 0.9.26, however, 0.9.25 is installed. > > >> Are there any plans on upgrading Bundler on the bamboo stack or are > >> there other ways around? > > >> Thanks, > > >> Ariejan de Vroomhttp://ariejan.net > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: rails-3.0.0.beta4 on bamboo-ree-1.8.7?
Curious to see the update too! On Jun 11, 4:43 am, Pedro Belo wrote: > Hey guys! > > Thanks for reporting. We're aware we need to update Bundler - we'll > roll that out asap! > > On Thu, Jun 10, 2010 at 7:37 PM, Chris Hanks > > > > wrote: > > I'm anxious for Bundler 0.9.26 also! > > > On Jun 9, 3:31 am, Ariejan de Vroom wrote: > >> Hey, > > >> I'm running into a Bundler/Rails issue when trying to deploy a Rails > >> 3.0.0.beta4 app to the bamboo-ree-.1.8.7 stack. Rails 3b4 need bundler > >> 0.9.26, however, 0.9.25 is installed. > > >> Are there any plans on upgrading Bundler on the bamboo stack or are > >> there other ways around? > > >> Thanks, > > >> Ariejan de Vroomhttp://ariejan.net > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
