Rails 2.3
does not have asset pipeline. So there is no need to precompile assets. Your assets should already be located in the Rails.root/public/stylesheets
folder
Anything in Rails.root/public/
folder is served by the web server
directly and it does not involve rails.
Your problem is most likely some sort of caching. You can try fetching the stylesheet directly using its URL like this
http://server.domain/stylesheets/mystyles.css
and see if your changes are reflected.
You can also check your Firebug
-> Net
tab to see if the style sheet is being downloaded from the server (http return code: 200 OK
) or it is being picked up from the cache (http return code: 304 Not Modified
)
There are ways to handle this type of issues, which rails 3.1 asset pipeline
incorporates.
- Using a different file name when content changes
- Using the ETag header
- Appending a unique hash (calculated using timestamp of the file) as a
query string
. For examplehttp://domain/style.css?djfhsfhkkjdsfh
wheredjfhsfhkkjdsfh
will change every timestyle.css
is modified.
are couple of commonly used tricks.
If you are keen on using asset pipeline with rails 2.3
you have options such as Jammit