Added the RoR Login-Engine and activated it on the site.

[selectricity-live] / vendor / plugins / engines / generators / engine / templates / README

diff --git a/vendor/plugins/engines/generators/engine/templates/README b/vendor/plugins/engines/generators/engine/templates/README
new file mode 100644 (file)
index 0000000..4d2371c
--- /dev/null
+++ b/vendor/plugins/engines/generators/engine/templates/README
@@ -0,0 +1,85 @@
+------------------[ once you've read this, delete it ]---------------------
+
+ENGINE DEVELOPERS - HEED THIS!
+
+This is a sample README file to guide your users when they are installing what is undoubtedly going to be the finest piece of code they ever got their hands on. Lucky them, but alas they are often foolish, and so this is where you can guide them with the metaphorical beating of twigs. Or just a numbered series of instructions.
+
+ANYWAY - you will almost certainly need to tailor this to your specific engine. For instance, your users will probably only need to include modules into the ApplicationController and ApplicationHelper if your engine defines methods to be usable by controllers and views external to your engine.
+
+If you engine does not rely on any database tables, you will probably not need migrations either.
+
+You are also under no obligation to use the 'config' method for setting options within your modules. Documentation which explains the purpose of the 'config' method is available as part of the Engines plugin itself.
+
+Please check the engine development information on the Rails Engines wiki for more information about what to do now:
+  
+  http://rails-engines.rubyforge.org/wiki/wiki.pl?DevelopingAnEngine
+
+-----------------------[ remember to delete me! ]--------------------------
+
+= <%= engine_class_name %>
+
+<%= engine_class_name %> is a ...
+
+This software package is developed using the Engines plugin. To find out more about how to use engines in general, go to http://rails-engines.rubyforge.org for general documentation about the Engines mechanism.
+
+== Installation
+
+1. Create your Rails application, set up your databases, grab the Engines plugin and the <%= engine_class_name %>, and install them.
+
+2. Install the <%= engine_class_name %> into your vendor/plugins directory
+
+3. Modify your Engines.start call in config/environment.rb
+
+    Engines.start :<%= engine_start_name %> # or :<%= engine_underscored_name %>
+
+4. Edit your application.rb file so it looks something like the following:
+
+    class ApplicationController < ActionController::Base
+      include <%= engine_class_name %>
+    end
+
+5. Edit your application_helper.rb file:
+
+    module ApplicationHelper
+      include <%= engine_class_name %>
+    end
+
+6. Perform any configuration you might need. You'll probably want to set these values in environment.rb (before the call to Engines.start):
+
+    module <%= engine_class_name %>
+      config :some_option, "some_value"
+    end
+
+7. Initialize the database tables. You can either use the engine migrations by calling:
+
+    rake engine_migrate
+
+  to move all engines to their latest versions, or
+
+    rake engine_migrate ENGINE=<%= engine_start_name %>
+
+  to migrate only this engine.
+
+8. The <%= engine_class_name %> provides a default stylesheet and a small javascript helper file, so you'll probably want to include the former and almost certainly the latter in your application's layout. Add the following lines:
+
+      <%%= engine_stylesheet "<%=engine_start_name%>_engine" %>
+      <%%= engine_javascript "<%=engine_start_name%>_engine" %>
+
+== Configuration
+
+A number of configuration parameters are available to allow to you control
+how the data is stored, should you be unhappy with the defaults. These are
+outlined below. 
+
+  module <%= engine_class_name %>
+    config :some_option, "some_value"
+  end
+
+=== Configuration Options
++some_option+:: This option will set some_value 
+
+== Usage
+How to use this engine
+
+== License
+<%= license %>