Home/ Questions/Q 8863333
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T15:57:08+00:00

I have compiled assets using following command in rails 3.2 for production purpose. RAILS_ENV=production

  • 0

I have compiled assets using following command in rails 3.2 for production purpose.

RAILS_ENV=production bundle exec rake assets:precompile

After running above command an assets a folder is created under public. Now I want to removed non-compile assets folder because it is huge. But I have need answers to following questions.

  • Do I need the assets folder that contains non-compiled assets ?
  • If yes then what is purpose of having a non-compiled assets folder ?

I will appreciate your help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, keep them.

    The purpose is that when they are taken from assets to public they are usually minified and combined, greatly saving space and helping to reduce download time for end users when using the site. But when you need to make changes, use the originals in assets.

    In development mode (local, on your box), the assets version is used and is useful in traces while developing/debugging as they point to the actual source code lines in question and have the original (usually longer and meaningful) variable names.

    • 0