Public and assets folders in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of the public folder in Rails

What is the main role of the public folder in a Rails application?

A It contains Ruby source code files for models and controllers.

B It holds compiled assets like JavaScript and CSS after precompilation.

C It stores static files that are served directly by the web server without Rails processing.

D It is used to store database migration files.

💡 Hint

Think about files that the server can send without running Ruby code.

The public folder holds static files like images, robots.txt, or favicon.ico that the web server can serve directly without involving Rails code.

❓ component_behavior

intermediate

Behavior of assets in the assets folder

Which statement best describes how files in the app/assets folder are handled in a Rails app?

A They contain only Ruby code for asset management.

B They are served directly by the web server without any processing.

C They are ignored by Rails and must be manually copied to the public folder.

D They are compiled and served through the asset pipeline, allowing preprocessing and fingerprinting.

💡 Hint

Consider how Rails prepares CSS and JavaScript files before sending them to the browser.

Files in app/assets are processed by the asset pipeline. This allows Rails to preprocess, compress, and fingerprint them for caching.

📝 Syntax

advanced

Correct asset reference in Rails views

Which option correctly references an image named logo.png stored in app/assets/images inside a Rails ERB view?

Ruby on Rails

<%= ??? %>

A <%= asset_path('logo.png') %>

B <%= image_tag 'logo.png' %>

C <%= image_path('logo.png') %>

D <%= image_url('logo.png') %>

💡 Hint

Think about the helper that generates an HTML tag.

image_tag generates an HTML element with the correct path to the asset. The others return just the URL or path string.

🔧 Debug

advanced

Why is a new image not showing in production?

You added new_image.png to app/assets/images but it does not appear in production after deployment. What is the most likely cause?

A The asset pipeline was not recompiled, so the new image is missing in the precompiled assets.

B The image file is in the wrong folder; it should be in public/images.

C Rails does not support PNG images in assets.

D The image tag helper is deprecated and does not work.

💡 Hint

Think about what happens to assets when deploying to production.

In production, Rails serves precompiled assets. If you add a new asset, you must recompile assets so the new file is included.

❓ state_output

expert

Result of accessing a file in public vs assets folder

Given a file named example.txt placed in both public and app/assets folders, what happens when a browser requests /example.txt in production?

A The file from the public folder is served directly; the asset pipeline ignores the request.

B The asset pipeline serves the file from app/assets with fingerprinting applied.

C Rails returns a 404 error because the file exists in two places.

D The file from app/assets is served without fingerprinting.

💡 Hint

Remember how the web server handles files in public vs assets folders.

Files in the public folder are served directly by the web server. Requests to /example.txt will return the public file, ignoring app/assets.

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