forked from kwatch/docrails
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Deletes trailing whitespaces (over text files only find * -type f -ex…
…ec sed 's/[ \t]*$//' -i {} \;)
- Loading branch information
1 parent
1590377
commit b451de0
Showing
337 changed files
with
2,122 additions
and
2,124 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ are used to consolidate code for sending out forgotten passwords, welcome | |
wishes on signup, invoices for billing, and any other use case that requires | ||
a written notification to either a person or another system. | ||
|
||
Action Mailer is in essence a wrapper around Action Controller and the | ||
Action Mailer is in essence a wrapper around Action Controller and the | ||
Mail gem. It provides a way to make emails using templates in the same | ||
way that Action Controller renders views using templates. | ||
|
||
|
@@ -23,7 +23,7 @@ This can be as simple as: | |
|
||
class Notifier < ActionMailer::Base | ||
delivers_from '[email protected]' | ||
|
||
def welcome(recipient) | ||
@recipient = recipient | ||
mail(:to => recipient, | ||
|
@@ -36,13 +36,13 @@ ERb) that has the instance variables that are declared in the mailer action. | |
|
||
So the corresponding body template for the method above could look like this: | ||
|
||
Hello there, | ||
Hello there, | ||
|
||
Mr. <%= @recipient %> | ||
|
||
Thank you for signing up! | ||
And if the recipient was given as "[email protected]", the email | ||
|
||
And if the recipient was given as "[email protected]", the email | ||
generated would look like this: | ||
|
||
Date: Mon, 25 Jan 2010 22:48:09 +1100 | ||
|
@@ -55,7 +55,7 @@ generated would look like this: | |
charset="US-ASCII"; | ||
Content-Transfer-Encoding: 7bit | ||
|
||
Hello there, | ||
Hello there, | ||
|
||
Mr. [email protected] | ||
|
||
|
@@ -75,7 +75,7 @@ Or you can just chain the methods together like: | |
== Receiving emails | ||
|
||
To receive emails, you need to implement a public instance method called <tt>receive</tt> that takes a | ||
tmail object as its single parameter. The Action Mailer framework has a corresponding class method, | ||
tmail object as its single parameter. The Action Mailer framework has a corresponding class method, | ||
which is also called <tt>receive</tt>, that accepts a raw, unprocessed email as a string, which it then turns | ||
into the tmail object and calls the receive instance method. | ||
|
||
|
@@ -90,21 +90,21 @@ Example: | |
|
||
if email.has_attachments? | ||
for attachment in email.attachments | ||
page.attachments.create({ | ||
page.attachments.create({ | ||
:file => attachment, :description => email.subject | ||
}) | ||
end | ||
end | ||
end | ||
end | ||
|
||
This Mailman can be the target for Postfix or other MTAs. In Rails, you would use the runner in the | ||
This Mailman can be the target for Postfix or other MTAs. In Rails, you would use the runner in the | ||
trivial case like this: | ||
|
||
rails runner 'Mailman.receive(STDIN.read)' | ||
|
||
However, invoking Rails in the runner for each mail to be received is very resource intensive. A single | ||
instance of Rails should be run within a daemon if it is going to be utilized to process more than just | ||
However, invoking Rails in the runner for each mail to be received is very resource intensive. A single | ||
instance of Rails should be run within a daemon if it is going to be utilized to process more than just | ||
a limited number of email. | ||
|
||
== Configuration | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.