Skip to content

Latest commit

 

History

History
103 lines (77 loc) · 3.07 KB

README.md

File metadata and controls

103 lines (77 loc) · 3.07 KB
Raw

Asset Pipeline Poem

Objectives
Explore the assets pipeline in rails
Practice structuring require statements
Precompile compressed javascript assets

Terms:

  • Manifest
  • Pre/compilation
  • Concatenation
  • Compression / Minification
  • Browser Caching
  • MD5 fingerprint

##Instructions: Your goal is to reconstruct a simple poem.

  • Clone this repo
    • Note that this rails app does not have a database.
  • Run your server and open "/". You should see a jumbled poem.

When you're done make changes, the homepage should look like this (with the poem in the correct order and styled correctly):

goal

Rules

  • You are not allowed to modify any files.
  • You are only allowed to update the manifests in:
    • app/assets/javascripts/application.js
      • e.g. //= require roses-are-red
    • app/assets/stylesheets/application.css
      • e.g. *= require layout
  • Try not to use require_tree . anywhere.

Part 1. Using the Asset Pipeline

The assets you want live in the following locations, inside of your rails application directory:

app/                    # application specific code
    assets/
        images/
        javascripts/
        stylesheets/
lib/                    # custom libraries
    assets/
        javascripts/
        stylesheets/
vendor/                 # third party libraries
    assets/
        javascripts/
        stylesheets/

Each directory has a specific use-case. The files you want are scattered across them. Your goal is to find all the files and require them in the correct order!

Part 2. Precompilation

Your solution should also work in production!

First, we need to precompile our assets.

rake assets:precompile

After running rake assets:precompile, your concatenated/compressed assets will live in:

public/
    assets/

Next, we need to run our server in production:

SECRET_KEY_BASE=shhhh RAILS_SERVE_STATIC_FILES=true rails server -e production

Now when you use "view source" in the chrome console, you should see one application-12345.js file, and one application-abcde.css file. That last bit is called a "fingerprint" and it's used for caching.

Whenever you change a javascript or css file, you need to:

  1. precompile your assets again
  2. restart your server

The fingerprint will change whenever the file changes. Use view-source to see it!

When in doubt, start fresh:

  • Delete tmp/cache/assets/
  • Delete public/assets/
  • ( OR, you can just run: rake assets:clobber )
  • And restart your server!!!

##Bonuses: Note that reset.css is being included using a CDN. It's a quick and dirty way of including it, but let's save it locally:

  1. Find and copy the current reset.css url (see views/layouts/application.html.erb)
  2. cd vendor/assets/stylesheets/
  3. curl -vs RESET_CSS_URL > reset.css
  4. Finally, delete the old cdn link, and "require" the new reset in your application.css manifest.

##Reading http://guides.rubyonrails.org/asset_pipeline.html https://github.com/rails/sprockets#sprockets-directives