rails 3.2 on heroku; asset precompilation problems

Hi, I'm having a bear of a time upgrading a pre-3.1 rails app to 3.2. I'ts working locally, but on heroku no matter what I do, I get exceptions on pageload: A ActionView::Template::Error occurred in posts#index: application.css isn't precompiled Initially it wouldn't compile at all; per heroku

Re: rails 3.2 on heroku; asset precompilation problems

milar problem. I am 100% positive > I have public/assets/manifest.yml in my master branch. But when pushed to > heroku, it doesn't see it. And of course the app won't run because compiled > assets are missing. > > Please let me know if you have found a solution. > > > On

Re: serving wong version ??

Have you ever run a `heroku rollback`? `rollback` will cause heroku to serve an older slug, but it won't have any impact at all on what commit the `master` branch points to. You can use `heroku releases` to get a clearer picture of what commit heroku thinks it's supposed to be serving. Of course,

Re: Assets Precompile: Works Locally, Heroku Skips Some Files

Hi Karl, Is there anything in your .slugignore? I was having the same problem with an app where I had an assets/ in the rails-root that contained some development assets (.psd and the like), and so I had `assets` in my .slugignore. Removing that line made heroku behave. On Thu, Mar 22, 2012 at 11

Re: Assets Precompile: Works Locally, Heroku Skips Some Files

haha YES, simulsolve On Thu, Mar 22, 2012 at 8:13 PM, Karl wrote: > Well, I figured it out. The problem is with my .slugignore file. In > .slugignore I had: > > spec/**/* > > assets/**/* > > > Why? I used to keep some photoshop files in there. But the /assets folder > doen't exist any more. > >

postgres connection problems

I've been having intermittent pg connection problems since my app was migrated to the new database setup. I'll get a pair of exceptions (see below). Sometimes the problem fixes itself in a couple of minutes; other times I have to do a `heroku restart`. The first exception that comes through is a "

Re: postgres connection problems

has only happened since the db update as well. > > Please let me know what you've learned. Thanks! > > -Wendy > > > > On Wednesday, November 21, 2012 11:20:07 AM UTC-5, Andrew Lorente wrote: >> >> I've been having intermittent pg connection prob

Re: postgres connection problems

error is connection time out and the next is eof detected. The site >>> is then down for a while... happened twice today, took 16 min to resolve. >>> At least now I know I can do 'heroku restart' I hadn't thought of that. It >>> has only happened since th

Re: Database migration error

Hi Harper, I'm just looking for clarification on what you mean when you say "I also made sure to store it in the DATABASE_URL config var per Heroku's instructions." What is it that you put there? Just your HEROKU_POSTGRESQL_color_URL, or something else? Andrew On Thu, Dec 6, 2012 at 5:16 AM, H

Ask a web dyno if it is currently up, from the outside?

Hi, I'm writing a commandline client that consumes a web api that currently lives in a single web dyno. I'd like the client to be able to tell the user "hey the dyno is starting up; it'll be a second." Short of having the heroku credentials and asking heroku directly, is there any way to get that

Re: Ask a web dyno if it is currently up, from the outside?

t if its taking more than a couple of seconds that this is the >> case? >> >> >> On Wednesday, December 26, 2012, Andrew Lorente wrote: >> >>> Hi, >>> >>> I'm writing a commandline client that consumes a web api that currently >>> lives in

Scaling worker dynos from the command line?

The heroku command-line client is giving me some mixed signals! $ heroku help ps:scale Usage: heroku ps:scale DYNO1=AMOUNT1 [DYNO2=AMOUNT2 ...] scale dynos by the given amount Examples: $ heroku ps:scale web=3 worker+1 Scaling web dynos... done, now running 3 Scaling worker dyno

Re: Scaling worker dynos from the command line?

2013 at 7:59 PM, Daniel Farina wrote: > On Sun, Jul 7, 2013 at 7:53 PM, Andrew Lorente > wrote: > > The heroku command-line client is giving me some mixed signals! > > > > $ heroku help ps:scale > > Usage: heroku ps:scale DYNO1=AMOUNT1 [DYNO2=AMOUNT2 ...] &g

Re: Heroku Migration not working

Yeah it sounds like your migrations don't apply cleanly from scratch. You could track down the errant one, or `heroku run rake db:schema:load` might bypass the problem. On Wed, Feb 5, 2014 at 7:56 PM, Robert Fletcher wrote: > Oh, looks like you're trying to drop a table that doesn't exist. Do yo

Re: image_optim 0.17 giving errors: pngquant worker: `pngquant` not found; not found during image upload

Going through the [1]changelog, it looks like 0.17.0 increased image_optim's eagerness to fail when it can't find the path of a worker. It looks like you may be able to disable the problem workers when you initialize ImageOptim: ImageOptim.new(:pngqant => false, :jpegtran => false, :svgo => fals

Re: image_optim 0.17 giving errors: pngquant worker: `pngquant` not found; not found during image upload

Oh! Well, I haven't used it myself, but it looks like [1]Vulcan is what you're looking for. -- Andrew On Mon, Oct 6, 2014, at 12:56 PM, Andrew Lorente wrote: Oh! Well, I haven't used it myself, but it looks like [2]Vulcan is what you're looking for. -- Andrew