Public and assets folders in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the public folder in a Rails application?

The public folder holds static files like images, robots.txt, and favicon.ico that are served directly by the web server without going through Rails.

beginner

Where should you put CSS, JavaScript, and image files that need preprocessing in Rails?

These files belong in the app/assets folder because Rails processes them with tools like the asset pipeline before serving.

intermediate

How does Rails handle files in the public folder differently from those in app/assets?

Files in public are served as-is, no processing. Files in app/assets are compiled, minified, and fingerprinted by the asset pipeline before serving.

intermediate

What is the benefit of fingerprinting assets in Rails?

Fingerprinting adds a unique hash to filenames to help browsers cache assets efficiently and update them only when the file changes.

beginner

Can you put dynamic Ruby code inside files in the public folder?

No. Files in public are static and served directly. Dynamic Ruby code belongs in views or helpers, not in public.

Which folder in Rails is used for static files served without processing?

A public

B app/assets

C config

D lib

The public folder holds static files served directly by the web server.

Where do you place JavaScript files that need to be compiled by Rails?

A bin

B public

C app/assets

D tmp

JavaScript files that need preprocessing go in app/assets.

What does fingerprinting in Rails asset pipeline help with?

A Improving database queries

B Caching assets efficiently

C Generating HTML templates

D Running background jobs

Fingerprinting helps browsers cache assets and update them only when they change.

Can you put ERB (Ruby code) inside files in the public folder?

A No, files are served as static

B Yes, it will be processed

C Only if the file is .html.erb

D Only in development mode

Files in public are static and not processed by Rails.

Which folder is best for storing images that need to be optimized by Rails?

A log

B public

C vendor

D app/assets/images

Images in app/assets/images are processed by the asset pipeline.

Explain the difference between the public folder and the app/assets folder in Rails.

Think about how files are served and processed.

Why is fingerprinting important for assets in Rails? How does it affect caching?

Consider how browsers decide to use cached files or fetch new ones.

Practice

1. What is the main purpose of the public folder in a Rails application?

easy

A. To store static files served directly without processing

B. To hold Ruby code files for controllers and models

C. To keep database migration files

D. To store files that Rails compiles before sending

Solution

1. Step 1: Understand the role of the public folder

   The public folder contains files like images, HTML, or JavaScript that Rails serves directly to the browser without any processing.

2. Step 2: Compare with other folders

   The assets folder is for files Rails processes (like compiling CSS or JavaScript), so it is not the public folder's role.

3. Final Answer:

   To store static files served directly without processing -> Option A

4. Quick Check:

   Public folder = static files served directly [OK]

Hint: Public folder serves files as-is, no processing needed [OK]

Common Mistakes:

• Confusing public with assets folder
• Thinking public holds Ruby code
• Assuming public processes files before serving

2. Which of the following is the correct path to place a CSS file that Rails will precompile and serve?

easy

A. app/public/stylesheets/style.css

B. public/assets/stylesheets/style.css

C. app/assets/stylesheets/style.css

D. config/assets/stylesheets/style.css

Solution

1. Step 1: Identify the standard assets folder for stylesheets

   Rails expects CSS files to be inside app/assets/stylesheets for precompilation and processing.

2. Step 2: Eliminate incorrect paths

   The public folder is for static files, not processed assets. The config folder does not hold assets.

3. Final Answer:

   app/assets/stylesheets/style.css -> Option C

4. Quick Check:

   CSS in assets/stylesheets = app/assets/stylesheets/style.css [OK]

Hint: Assets folder is inside app/, not public or config [OK]

Common Mistakes:

• Placing CSS directly in public folder
• Using wrong folder like config/assets
• Confusing assets with public folder paths

3. Given a file logo.png placed inside public/images, what URL path will serve this image in a Rails app?

medium

A. /assets/images/logo.png

B. /public/images/logo.png

C. /app/assets/images/logo.png

D. /images/logo.png

Solution

1. Step 1: Understand how public folder maps to URL

   Files inside public are served from the root URL path. So public/images/logo.png is accessible at /images/logo.png.

2. Step 2: Eliminate other options

   /assets/images/logo.png is for assets pipeline files, not public. /public/images/logo.png and /app/assets/images/logo.png are not valid URL paths.

3. Final Answer:

   /images/logo.png -> Option D

4. Quick Check:

   Public folder maps directly to root URL [OK]

Hint: Public folder files appear at root URL path [OK]

Common Mistakes:

• Using /assets prefix for public files
• Including 'public' in URL path
• Confusing assets and public URL paths

4. You placed a JavaScript file in app/assets/javascripts but it is not loading in your Rails app. What is a likely cause?

medium

A. You forgot to include the JavaScript pack or manifest in your layout

B. The file is missing from the public folder

C. JavaScript files must be placed in public/javascripts

D. Rails does not support JavaScript in assets folder

Solution

1. Step 1: Check how assets are loaded in Rails

   Files in app/assets/javascripts need to be referenced in your layout via a manifest or pack tag to load properly.

2. Step 2: Eliminate incorrect causes

   JavaScript files do not belong in public for processing. Rails fully supports JavaScript in assets folder.

3. Final Answer:

   You forgot to include the JavaScript pack or manifest in your layout -> Option A

4. Quick Check:

   Assets must be linked in layout to load [OK]

Hint: Always include asset manifests or packs in your layout [OK]

Common Mistakes:

• Expecting assets to load without linking in layout
• Placing JS files in wrong folders
• Thinking public folder is for processed assets

5. You want to add a favicon to your Rails app that loads instantly without asset pipeline processing. Where should you place the favicon file and how should you reference it in your HTML?

hard

A. Place in app/assets/images and use <%= favicon_link_tag 'favicon.ico' %>

B. Place in public folder root and use <link rel='shortcut icon' href='/favicon.ico'>

C. Place in app/assets/images and use <link rel='icon' href='/assets/favicon.ico'>

D. Place in public/images and use <%= image_tag 'favicon.ico' %>

Solution

1. Step 1: Choose folder for instant loading without processing

   Files in public are served directly, so placing favicon.ico in public root ensures instant loading.

2. Step 2: Reference favicon correctly in HTML

   Use a standard HTML <link> tag with href pointing to /favicon.ico for browsers to find it.

3. Final Answer:

   Place in public folder root and use <link rel='shortcut icon' href='/favicon.ico'> -> Option B

4. Quick Check:

   Favicon in public root + direct link = Place in public folder root and use <link rel='shortcut icon' href='/favicon.ico'> [OK]

Hint: Put favicon in public root and link with standard HTML tag [OK]

Common Mistakes:

• Placing favicon in assets and expecting instant load
• Using image_tag instead of link tag for favicon
• Referencing wrong URL path for favicon