I’m working on my first-ever rails project. More accurately, I’m maintaining and modifying someone else’s, which is the best way to learn a new platform, so I can’t really complain, but it’s also one of the more frustrating ways to learn from time to time. I’m going to try to post all the solutions to my frustrations here, though I’m sure I’ll miss some due to time constratints (I have in fact already missed some due to time constraints).
And that, ladies and gents, was my introduction to the asset-packager. A quick google of that function name found me all I needed to know.
But here’s what I’m posing about. Apparently there’s a process to this: first you run
to make sure that the asset-packager tasks are tasks that rake knows about. For me they were. Then you run
to create the yaml file that defines all the assets you want to package. When I did that, it told me it was way ahead of me – already has it one of those. Ok, then.
CHOKE! I get:
No such file or directory - /var/www/app/current/tmp/base_packaged_uncompressed.js
I know this is kind of a n00b post – but then I’m a Rails n00b struggling to get a Rails 2.3/Ruby 1.8 app running in this Rails 3.2/Ruby 1.9 world – and as we all well know, Ruby’s a lot of great things, but one thing it’s not is backward compatible. So it’s an uphill battle when you’re new. Hopefully someone else who’s new can benefit from this – and all the other entries in what is likely to turn into a series.