From 454492dfd7d364bb4386935bd8d5f636d5163e2b Mon Sep 17 00:00:00 2001 From: Ryan Bigg Date: Thu, 6 Oct 2011 18:20:38 +1100 Subject: [engines guide] Credit where credit is due --- railties/guides/source/engines.textile | 2 ++ 1 file changed, 2 insertions(+) (limited to 'railties/guides/source/engines.textile') diff --git a/railties/guides/source/engines.textile b/railties/guides/source/engines.textile index ddd2e50a6c..ce041141a0 100644 --- a/railties/guides/source/engines.textile +++ b/railties/guides/source/engines.textile @@ -22,6 +22,8 @@ Engines can also be isolated from their host applications. This means that an ap To see demonstrations of other engines, check out "Devise":https://github.com/plataformatec/devise, an engine that provides authentication for its parent applications, or "Forem":https://github.com/radar/forem, an engine that provides forum functionality. +Finally, engines would not have be possible without the work of James Adam, Piotr Sarnacki, the Rails Core Team, and a number of other people. If you ever meet them, don't forget to say thanks! + h3. Generating an engine To generate an engine with Rails 3.1, you will need to run the plugin generator and pass it the +--mountable+ option. To generate the beginnings of the "blorgh" engine you will need to run this command in a terminal: -- cgit v1.2.3