# asset\_pipeline Published articles for asset\_pipeline. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Another Day, Another Missing Image from Asset Pipeline DevFeed: [Another Day, Another Missing Image from Asset Pipeline]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-06-04T09:21:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Web Development]() Tags: [asset-pipeline](), [compiler](), [rails]() ### AI overview A personal account of troubleshooting a missing JPEG in a Rails 6 application. The image existed, was referenced like other images, and was produced by the asset compiler, but changing a setting from false to true made it render; the author says the underlying cause remains unclear. ### Source excerpt The asset pipeline is the component of Rails that I, well, let me quote myself from a recent email: I've been tracking down that crazy image related issue for an age now and I think I just got it. Every single time it is always the damn asset pipeline (this is the one component in Rails that I have a literal deep and abiding hatred for; it is finicky code and instead of sticking with a solution they keep replacing it which I have the deep suspicion means that the heisenbugs keep migrating). I hit this again recently with this kind of crap: I, [2022-06-04T09:11:21.177736 #7055] INFO -- : [b4a4b65f-beb6-437b-b465-8cdf93a3b00d] Rendering errors/error_500.html.erb within layouts/application I, [2022-06-04T09:11:21.177896 #7055] INFO -- : [b4a4b65f-beb6-437b-b465-8cdf93a3b00d] Rendered errors/error_500.html.erb within layouts/application (Duration: 0.0ms | Allocations: 5) I, [2022-06-04T09:11:21.179045 #7055] INFO -- : [b4a4b65f-beb6-437b-b465-8cdf93a3b00d] Rendered layouts/_meta_tags.html.erb (Duration: 0.1ms | Allocations: 11) I, [2022-06-04T09:11:21.179779 #7055] INFO -- : [b4a4b65f-beb6-437b-b465-8cdf93a3b00d] Rendered layouts/_header.html.erb (Duration: 0.4ms | Allocations: 119) I, [2022-06-04T09:11:21.180298 #7055] INFO -- : [b4a4b65f-beb6-437b-b465-8cdf93a3b00d] Rendered layouts/_footer.html.erb (Duration: 0.1ms | Allocations: 27) I, [2022-06-04T09:11:21.180679 #7055] INFO -- : [b4a4b65f-beb6-437b-b465-8cdf93a3b00d] Completed 500 Internal Server Error in 8ms (Views: 3.2ms | Allocations: 2093) I, [2022-06-04T09:16:21.177692 #7055] INFO -- : [bde57e27-882b-44ff-922c-a74f218bd4e6] Started HEAD "/" for 208.115.199.28 at 2022-06-04 09:16:21 +0000 I, [2022-06-04T09:16:21.178505 #7055] INFO -- : [bde57e27-882b-44ff-922c-a74f218bd4e6] Processing by HomeController#index as HTML I, [2022-06-04T09:16:21.179534 #7055] INFO -- : [bde57e27-882b-44ff-922c-a74f218bd4e6] Rendering home/index.html.erb within layouts/application I, [2022-06-04T09:16:21.179763 #7055] INFO -- : [bde57 ## When Rails 7 Doesn't Process application.js DevFeed: [When Rails 7 Doesn't Process application.js]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-04-22T22:28:00Z Content type: article Language: en Sources: [Scott Johnson]() Topics: [Rails](), [JavaScript](), [Bootstrap](), [modern web development]() Tags: [asset-pipeline](), [bootstrap](), [javascript](), [modern-web-development](), [pipeline](), [rails]() ### AI overview A troubleshooting post about a Rails 7 application in which Bootstrap popovers did not work because application.js appeared not to be processed or included in the page source. The author discusses tracing the issue to JavaScript and the asset pipeline, but the supplied text ends before the resolution. ### Source excerpt This is more than a mildly embarrassing post to have to write but it is an interesting example of how habits can bite you hard - so, so hard. I recently wanted to start on an application and actually be current on everything: Rails, Bootstrap, etc. I have long admitted to having issues with respect to "modern" web development (specifically JavaScript / the asset pipeline) and I'm mildly starting to deal with those issues. I began with a BootrAils tutorial and started to work through it. I got all the way to the end and I noticed that I simply could NOT get the popovers to work. I don't claim to have a great understanding of the asset pipeline but I do know that it is a preprocessor that should get invoked on every page request. I traced the problem back to application.js seemingly not getting processed (a view source didn't show it). So, just to be sure, I added this to application ## Rails 6 - Can't Find Application.js DevFeed: [Rails 6 - Can't Find Application.js]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2021-12-18T14:51:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Yarn](), [Development]() Tags: [asset-pipeline](), [bash](), [command](), [compilation](), [foreman](), [git](), [js](), [rails](), [rake]() ### AI overview A troubleshooting note about a Rails 6 project where Webpacker cannot find application.js. It explains installing Webpacker and using bin/dev with Foreman so the JavaScript and CSS asset processes run. ### Source excerpt So I started fiddling about with a new Rails project and after finding a likely starting point, I immediately ended up with this: Webpacker can't find application.js in I'm old school Rails and I find the whole asset compilation situation, honestly, perplexing. The solution turned out to be: bundle exec rails webpacker:install after the normal: git clone foo bundle install bundle exec rake db:migrate I have no idea why the bundler install doesn't handle executing webpacker:install but cie la vie. The more things change, the more they stay the same ... Update: I kept at this and kept finding that I didn't have webpacker or some other portion of the rails stack running. I finally traced this down to things having changed. Traditionally I've always run rails as: bundle exec rails s -pXYZ And the new approach is to run: bin/dev which in turn contains: #!/usr/bin/env bash if ! command -v foreman &> /dev/null then echo "Installing foreman..." gem install foreman fi foreman start -f Procfile.dev "$@" and the Procfile.dev file contains: web: bin/rails server -p 3000 js: yarn build --watch css: yarn build:css --watch I was literally missing the yarn command so part of the overall asset pipeline just wasn't running. Old habits die hard. ## Rails Asset Pipeline Failures and Capistrano DevFeed: [Rails Asset Pipeline Failures and Capistrano]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-04-14T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Deployment](), [Amazon Web Services](), [Ansible](), [Jenkins](), [CI/CD]() Tags: [ansible](), [asset-pipeline](), [aws](), [capistrano](), [ci-cd](), [deploy](), [deployment](), [jenkins](), [rails]() ### AI overview The author describes troubleshooting a Rails application deployment on AWS after HatchBox failed and a Capistrano deployment appeared successful but produced a CSS-related 500 error. The article discusses a planned deployment approach involving Jenkins, Ansible, Capistrano, and other tools, but the supplied text does not include the final diagnosis or resolution. ### Source excerpt One of the single worst parts of being a one man show on an engineering effort is that when you hit a serious snag, well, you're fscked. I'm at the death march phase of a project, that wonderful stage, where you're so far into it that you can see the end but it seemingly never arrives - like the speed of light, it feels like you can never quite get there. Pro Tip: At this stage being asked by your manager, on a continuous basis, "anything that you can show me" is not helpful. It is actually an antipattern which simply slows the project by making the engineer feel even worse (yes I'm late and I can argue for scope creep, etc but I'll own it and I'm still late). Anyway I recently went through this with respect to getting a complex Rails code base deployed onto AWS. I started with my usual deploy tool of HatchBox but nothing worked and it was in the wee hours, and over a weekend, when I had no right to expect timely technical support so I figured "Ok I'll do a raw deploy with Capistrano" - and then the cluster fsck began in earnest. One of the general rules of technology is that everything is a two edged sword and where you get something, you give something. For example C gives outstanding performance and flexibility but it also can be a source of security issues, pointer bugs, buffer overflows, etc. Similarly Rails, even today, gives you: an unprecedentedly easy way to build web apps (provided you do it the Rails way) but deployment of modern Rails apps can be one of the most cursing laden experiences I've ever had The only easy way I've ever found to deploy Rails apps is HatchBox and HatchBox wasn't actually a good fit for this application due to particularly complex, multi language CI / CD requirements (4 different git repos spanning, today, two languages). The real deployment approach is going to be a combination of Jenkins + Ansible that drive Capistrano plus some other deployment tools. But I digress and have now devolved into a large number of words, more words ## Gemify your assets DevFeed: [Gemify your assets]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2013-02-05T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Rails](), [rubygems](), [GitHub](), [Library]() Tags: [asset-pipeline](), [github-repository](), [how-to](), [pipeline](), [rails](), [release](), [rubygems]() ### AI overview A tutorial on packaging JavaScript assets as a Ruby gem for use with the Rails 3.1 asset pipeline. It covers creating the gem structure, adding assets and a Rails engine, testing the gem in a Rails application, documenting it, and releasing it through GitHub and RubyGems. ### Source excerpt Rails 3.1 introduced the asset pipeline, which makes it easy to include versioned external assets as application dependencies.