parent
c5e083af3d
commit
e50719332e
|
@ -56,7 +56,7 @@ the comment operator on that line to later enable the asset pipeline:
|
|||
|
||||
To set asset compression methods, set the appropriate configuration options
|
||||
in `production.rb` - `config.assets.css_compressor` for your CSS and
|
||||
`config.assets.js_compressor` for your Javascript:
|
||||
`config.assets.js_compressor` for your JavaScript:
|
||||
|
||||
```ruby
|
||||
config.assets.css_compressor = :yui
|
||||
|
@ -781,7 +781,7 @@ exception indicating the name of the missing file(s).
|
|||
|
||||
#### Far-future Expires Header
|
||||
|
||||
Precompiled assets exist on the filesystem and are served directly by your web
|
||||
Precompiled assets exist on the file system and are served directly by your web
|
||||
server. They do not have far-future headers by default, so to get the benefit of
|
||||
fingerprinting you'll have to update your server configuration to add those
|
||||
headers.
|
||||
|
@ -943,7 +943,7 @@ gem.
|
|||
```ruby
|
||||
config.assets.css_compressor = :yui
|
||||
```
|
||||
The other option for compressing CSS if you have the sass-rails gem installed is
|
||||
The other option for compressing CSS if you have the sass-rails gem installed is
|
||||
|
||||
```ruby
|
||||
config.assets.css_compressor = :sass
|
||||
|
@ -1018,7 +1018,7 @@ The X-Sendfile header is a directive to the web server to ignore the response
|
|||
from the application, and instead serve a specified file from disk. This option
|
||||
is off by default, but can be enabled if your server supports it. When enabled,
|
||||
this passes responsibility for serving the file to the web server, which is
|
||||
faster. Have a look at [send_file](http://api.rubyonrails.org/classes/ActionController/DataStreaming.html#method-i-send_file)
|
||||
faster. Have a look at [send_file](http://api.rubyonrails.org/classes/ActionController/DataStreaming.html#method-i-send_file)
|
||||
on how to use this feature.
|
||||
|
||||
Apache and nginx support this option, which can be enabled in
|
||||
|
|
|
@ -254,7 +254,7 @@ $ rails generate scaffold HighScore game:string score:integer
|
|||
|
||||
The generator checks that there exist the directories for models, controllers, helpers, layouts, functional and unit tests, stylesheets, creates the views, controller, model and database migration for HighScore (creating the `high_scores` table and fields), takes care of the route for the **resource**, and new tests for everything.
|
||||
|
||||
The migration requires that we **migrate**, that is, run some Ruby code (living in that `20130717151933_create_high_scores.rb`) to modify the schema of our database. Which database? The sqlite3 database that Rails will create for you when we run the `rake db:migrate` command. We'll talk more about Rake in-depth in a little while.
|
||||
The migration requires that we **migrate**, that is, run some Ruby code (living in that `20130717151933_create_high_scores.rb`) to modify the schema of our database. Which database? The SQLite3 database that Rails will create for you when we run the `rake db:migrate` command. We'll talk more about Rake in-depth in a little while.
|
||||
|
||||
```bash
|
||||
$ rake db:migrate
|
||||
|
|
Loading…
Reference in New Issue