See the github repo at https://github.com/house9/puppet-solo-hello-world
Resources
- http://www.confreaks.com/videos/2479-railsconf2013-devops-for-the-rubyist-soul
- https://speakerdeck.com/jtdowney/devops-for-the-rubyist-soul-at-rubynation-2013
See the github repo at https://github.com/house9/puppet-solo-hello-world
Write-Ahead Logging (WAL) is a standard method for ensuring data integrity. A detailed description can be found in most (if not all) books about transaction processing. Briefly, WAL's central concept is that changes to data files (where tables and indexes reside) must be written only after those changes have been logged, that is, after log records describing the changes have been flushed to permanent storage. If we follow this procedure, we do not need to flush data pages to disk on every transaction commit, because we know that in the event of a crash we will be able to recover the database using the log: any changes that have not been applied to the data pages can be redone from the log records. (This is roll-forward recovery, also known as REDO.)
These examples were created using rails 3.2
NOTE: many email clients will ignore these headers
NOTE: many email clients will ignore these headers
NOTE: test against mail.header, not mail.headers
l = log -20 --format='%h %ad %d %an: %s' --date=shorttyping 'git l' renders the following output:
http {
# override to allow long query string
large_client_header_buffers 8 512k;
...
}
make_fk_unless_exists :projects, :milestone_id, :milestones
make_fk_unless_exists :tasks, :project_id, :projects
...