Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Rails 3.0.X, I would store my flash files in public/flash. Flash files such as: jwplayer, uploadify, etc.
With the introduction of the new directory structure in 3.1 (i.e. app/assets/), should flash files still be stored in public/flash or should I create a new directory called ‘flash’ in app/assets/ ?
if these are
.swffiles, I don’t think they belong inapp/assets. The asset folder allows for pre-“compiled” app asset files for CoffeeScript and SCSS (or similar js and css “compilers”). If you are compiling.asfiles into.swffiles as part of your deploy or startup process, I could see it making sense to put them in the asset folder. However, this seems like a horrible idea.=================UPDATE=====================
I was wrong. The asset folder is for serving Sprockets assets. As long as you can handle digested asset paths you should use Sprockets.