RubyGems - lockdown - Versions diffs - 0.4.6 → 0.5.0 - Mend

lockdown 0.4.6 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (48) hide show

data/website/index.html ADDED Viewed

@@ -0,0 +1,331 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+  <link rel="stylesheet" href="stylesheets/screen.css" type="text/css" media="screen" />
+  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+  <title>
+      Lockdown
+  </title>
+  <script src="javascripts/rounded_corners_lite.inc.js" type="text/javascript"></script>
+<style>
+</style>
+  <script type="text/javascript">
+    window.onload = function() {
+      settings = {
+          tl: { radius: 10 },
+          tr: { radius: 10 },
+          bl: { radius: 10 },
+          br: { radius: 10 },
+          antiAlias: true,
+          autoPad: true,
+          validTags: ["div"]
+      }
+      var versionBox = new curvyCorners(settings, document.getElementById("version"));
+      versionBox.applyCornersToAll();
+    }
+  </script>
+</head>
+<body>
+<div id="main">
+    <h1>Lockdown</h1>
+    <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/lockdown"; return false'>
+      <p>Get Version</p>
+      <a href="http://rubyforge.org/projects/lockdown" class="numbers">0.5.0</a>
+    </div>
+    <h2>What</h2>
+	<p>Lockdown is a authentication/authorization system for RubyOnRails (ver 2.x). While Merb functionality is in place, it is not complete.  There will be a release solely focused on getting the Merb functionality up to par with Rails.</p>
+	<h2>Installing</h2>
+<pre>
+$ sudo gem install lockdown
+$ cd &lt;your_project_directory&gt;
+$ lockdown .
+</pre>
+	<p>This will create a &#8220;lockdown&#8221; directory in the lib dir add two files: init.rb and session.rb.
+Modify init.rb to set configuration options and define the permissions and user groups that apply to your system.</p>
+	<p><strong> Please keep the following in mind:</strong>
+<ul>
+<li><strong>All Permissions are defined in init.rb, they cannot be defined via the administration screens.</strong></li>
+<li><strong>All User Groups should be defined in init.rb. The administration screens can be used to create user groups, but doing so should be reserved for the unexpected. Creating User Groups via the administration screens will only add more work for you if you want to run tests using those groups.</strong></li>
+<li><strong>Lockdown will sync up the rules (Permissions and User Groups) defined in init.rb with your database.  You can turn off this feature.</strong></li>
+</ul></p>
+	<p>To help you with your new application, Lockdown comes with a generator called lockdown that has various options for you to pick which templates you desire.</p>
+<pre>
+$ cd &lt;your_project_directory&gt;
+$ ./script/generate lockdown --all
+</pre>
+This will install resources such as:
+<ul>
+  <li>Models</li>
+  <li>Controllers</li>
+  <li>Views</li>
+  <li>Helpers</li>
+  <li>Migrations</li>
+  <li>Routes</li>
+</ul>
+	<p>Please refer to the <a href="generator.html">generator page</a> for more detail.</p>
+	<h2>How it works</h2>
+When Lockdown is installed, it adds the following line to your environment.rb (init.rb for Merb):
+<pre>
+  require "lockdown/init"
+</pre>
+This is the default init.rb included with Lockdown:
+<pre class='syntax'>
+<span class="ident">require</span> <span class="punct">&quot;</span><span class="string">lockdown</span><span class="punct">&quot;</span>
+<span class="ident">require</span> <span class="constant">File</span><span class="punct">.</span><span class="ident">join</span><span class="punct">(</span><span class="constant">File</span><span class="punct">.</span><span class="ident">dirname</span><span class="punct">(</span><span class="constant">__FILE__</span><span class="punct">),</span> <span class="punct">&quot;</span><span class="string">session</span><span class="punct">&quot;)</span>
+<span class="constant">Lockdown</span><span class="punct">::</span><span class="constant">System</span><span class="punct">.</span><span class="ident">configure</span> <span class="keyword">do</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment"># Configuration Options</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment"># Options with defaults:</span>
+  <span class="comment">#</span>
+  <span class="comment"># Set timeout to 1 hour:</span>
+  <span class="comment">#       options[:session_timeout] = (60 * 60)</span>
+  <span class="comment">#</span>
+  <span class="comment"># Set system to logout if unauthorized access is attempted:</span>
+  <span class="comment">#       options[:logout_on_access_violation] = false</span>
+  <span class="comment">#</span>
+  <span class="comment"># Set redirect to path on unauthorized access attempt:</span>
+  <span class="comment">#       options[:access_denied_path] = &quot;/&quot;</span>
+  <span class="comment">#</span>
+  <span class="comment"># Set redirect to path on successful login:</span>
+  <span class="comment">#       options[:successful_login_path] = &quot;/&quot;</span>
+  <span class="comment">#</span>
+  <span class="comment"># Set the system to sync the Permissions and UserGroups defined here</span>
+  <span class="comment"># with the database. </span>
+  <span class="comment">#       options[:sync_init_rb_with_db] = true</span>
+  <span class="comment">#</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment"># Define permissions</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment">#</span>
+  <span class="comment"># set_permission(:product_management, all_methods(:products))</span>
+  <span class="comment">#</span>
+  <span class="comment"># :product_management is the name of the permission which is later</span>
+  <span class="comment"># referenced by the set_user_group method</span>
+  <span class="comment">#</span>
+  <span class="comment"># :all_methods(:products) will return an array of all controller actions</span>
+  <span class="comment"># for the products controller</span>
+  <span class="comment">#</span>
+  <span class="comment"># if products is your standard RESTful resource you'll get:</span>
+  <span class="comment">#   [&quot;products/index , &quot;products/show&quot;,</span>
+  <span class="comment">#    &quot;products/new&quot;, &quot;products/edit&quot;,</span>
+  <span class="comment">#    &quot;products/create&quot;, &quot;products/update&quot;,</span>
+  <span class="comment">#    &quot;products/destroy&quot;]</span>
+  <span class="comment">#</span>
+  <span class="comment"># You can pass multiple parameters to concat permissions such as:</span>
+  <span class="comment">#      </span>
+  <span class="comment">#	  set_permission(:security_management,all_methods(:users),</span>
+  <span class="comment">#                                       all_methods(:user_groups),</span>
+  <span class="comment">#                                       all_methods(:permissions) )</span>
+  <span class="comment">#</span>
+  <span class="comment"># In addition to all_methods(:controller) there are:</span>
+  <span class="comment">#</span>
+  <span class="comment">#       only_methods(:controller, :only_method_1, :only_method_2)</span>
+  <span class="comment">#</span>
+  <span class="comment">#       all_except_methods(:controller, :except_method_1, :except_method_2)</span>
+  <span class="comment">#</span>
+  <span class="comment"># Some other sample permissions:</span>
+  <span class="comment"># </span>
+  <span class="comment">#  set_permission(:sessions, all_methods(:sessions))</span>
+  <span class="comment">#  set_permission(:my_account, only_methods(:users, :edit, :update, :show))</span>
+  <span class="comment"># </span>
+  <span class="comment"># Define your permissions here:</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment"># Built-in user groups</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment">#  You can assign the above permission to one of the built-in user groups</span>
+  <span class="comment">#  by using the following:</span>
+  <span class="comment"># </span>
+  <span class="comment">#  To allow public access on the permissions :sessions and :home:</span>
+  <span class="comment">#    set_public_access :sessions, :home</span>
+  <span class="comment">#     </span>
+  <span class="comment">#  Restrict :my_account access to only authenticated users:</span>
+  <span class="comment">#    set_protected_access :my_account</span>
+  <span class="comment">#</span>
+  <span class="comment"># Define the built-in user groups here:</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment"># Define user groups</span>
+  <span class="comment">#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span>
+  <span class="comment">#</span>
+  <span class="comment">#  set_user_group(:catalog_management, :category_management, </span>
+  <span class="comment">#                                      :product_management) </span>
+  <span class="comment">#</span>
+  <span class="comment">#  :catalog_management is the name of the user group</span>
+  <span class="comment">#  :category_management and :product_management refer to permission names</span>
+  <span class="comment">#</span>
+  <span class="comment"># </span>
+  <span class="comment"># Define your user groups here:</span>
+<span class="keyword">end</span>
+</pre>
+As you can see, the first line requires lockdown.  This will load the Lockdown system which consists of various parts:
+<ul>
+  <li>
+    Controller<br/>
+    <p>The controller functionality will add before filters to test each request agains the defined access_rights for the current user.  If the current request is not in the access_rights list, access right is denied.</p>
+  </li>
+  <li>
+    Model<br/>
+    <p>The model functionality will automatically set the updated_by/created_by fields of your model to the current_profile_id.</p>
+  </li>
+  <li>
+    View<br/>
+    <p>The view functionality intercepts the link_to method (aliases it).  If the current user does not have rights to the link, the link will not show.<br/>There is also a link_to_or_show method (same params as link_to) that will print out just the name of the link (no anchor tag) if the current user does not have access. </p>
+  </li>
+</ul>
+When referring to access rights: if you have a standard <span class="caps">REST</span> users controller, the access rights would be:
+<pre>
+  users/index
+  users/show
+  users/edit
+  users/update
+  users/new
+  users/create
+  users/destroy (delete for Merb)
+</pre>
+	<h2>The internals</h2>
+	<p>All configuration of Lockdown (Permissions and User Groups) are done in lib/lockdown/init.rb.  The database functionality is merely an extension of the definitions to allow for the dynamic creation of User Groups.  Permissions can not be created via the administration screens.</p>
+	<p>Lockdown doesn&#8217;t have a concept of Roles. Instead, Lockdown users can be associated to one or many User Groups to allow for flexibility.  In addition, you can use the admin screens to add new User Groups to the database. User groups are nothing more than a grouping mechanism for Permissions to ease management.</p>
+	<p>Here are the parts to Lockdown:</p>
+<div style="text-align:center">
+<img src="model.jpg" alt="" />
+</div>
+<ul>
+ <li><strong>Profiles</strong><br/>
+    <p>The profile model contains all non-user information related to person.  Lockdown uses the profile record as the reference for updated_by and created_by.  This allows you to remove the user record completely when you want to revoke access, but you still retain the foreign key for history.<br/>Here are the fields you have to start with:</p>
+    <ul>
+      <li>first_name : string</li>
+      <li>last_name : string</li>
+      <li>email : string</li>
+    </ul>
+<br/>
+  </li>
+ <li><strong>Users</strong><br/>
+    <p>The user model contains all user information related to person.<br/>Here are the fields you have to start with:</p>
+    <ul>
+      <li>login : string</li>
+      <li>crypted_password : string</li>
+      <li>salt : string</li>
+      <li>profile_id : integer</li>
+    </ul>
+<br/>
+  </li>
+ <li><strong>User Groups</strong><br/>
+    <p>User Groups exist only to group Permissions.  All functionality for your site should be covered by the user groups you define in init.rb.  You can use the admin screen to create new user groups if the need arises. The database model only has one field:  </p>
+    <ul>
+      <li>name : string</li>
+    </ul>
+<br/>
+  </li>
+ <li><strong>Permissions</strong><br/>
+    <p>Permissions are the security building blocks of your system and are defined in init.rb.  A permission maps to controller(s)/action(s) in your system. Please refer back to the documenation in init.rb on how to create permissions.
+ As permissions relate to system functionality, they cannot be created via the admin screen.  The database model only has one field:  </p>
+    <ul>
+      <li>name : string</li>
+    </ul>
+  </li>
+</ul>
+	<h2>Roadmap to 1.0</h2>
+	<p><strong>**this is tentative and the feature order may change</strong></p>
+<ul>
+  <li><strong>0.5.0: </strong>More generators to ease installation into existing projects</li>
+  <li><strong>0.6.0: </strong>Password reset/reminder, Registration page template generators</li>
+  <li><strong>0.7.0: </strong>OpenId support</li>
+  <li><strong>0.8.0: </strong>RSpec tests and helper methods for your application</li>
+  <li><strong>0.9.0: </strong>Merb Support</li>
+  <li><strong>1.0.0: </strong>Model level security</li>
+</ul>
+	<h2>Google Group</h2>
+	<p>If you are having a problem understanding how to use Lockdown, please post your question on the lockdown group.  If it&#8217;s documentation related, I will keep this page updated to help everyone.</p>
+	<p><a href="http://groups.google.com/group/stonean_lockdown?hl=en">http://groups.google.com/group/stonean_lockdown?hl=en</a></p>
+	<h2>How to submit patches</h2>
+	<p>The Clone <span class="caps">URL</span>: git://github.com/stonean/lockdown.git</p>
+	<p>Read the <a href="http://drnicwilliams.com/2007/06/01/8-steps-for-fixing-other-peoples-code/">8 steps for fixing other people&#8217;s code</a> and for section <a href="http://drnicwilliams.com/2007/06/01/8-steps-for-fixing-other-peoples-code/#8b-google-groups">8b: Submit patch to Google Groups</a>, use the Google Group above.</p>
+	<p>I&#8217;m new to git and this whole opensource project admin gig, so please be patient with my stumbling around.</p>
+	<h2>License</h2>
+	<p>This code is free to use under the terms of the <span class="caps">MIT</span> license.</p>
+	<h2>Contact</h2>
+	<p>Comments and suggestions are welcome via the <a href="http://groups.google.com/group/stonean_lockdown?hl=en">google group</a></p>
+	<p><a href="http://blog.stonean.com">Andrew Stone</a></p>
+    <p class="coda">
+      22nd May 2008<br/>
+      Theme extended from <a href="http://rb2js.rubyforge.org/">Paul Battley</a>
+    </p>
+</div>
+<script type="text/javascript">
+  var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
+  document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
+</script>
+<script type="text/javascript">
+  var pageTracker = _gat._getTracker("UA-4189092-1");
+  pageTracker._initData();
+  pageTracker._trackPageview();
+</script>
+</body>
+</html>

data/website/index.txt CHANGED Viewed

@@ -2,33 +2,31 @@ h1. <a href="http://lockdown.rubyforge.org">Lockdown</a>
 h2. What
-Lockdown is a authentication/authorization system for RubyOnRails (ver 2.x). While Merb functionality is in place, it is not complete.  There will be a release solely focused on getting the Merb functionality up to par with Rails.
+Lockdown is a authentication/authorization system for RubyOnRails (ver 2.x). While Merb functionality is in place, it is not complete.  There will be a release solely focused on getting the Merb functionality up to par with Rails.
 h2. Installing
-For the people who don't care to know the details and just want to get the system installed:
 <pre>
 $ sudo gem install lockdown
 $ cd <your_project_directory>
 $ lockdown .
 </pre>
-This will create a "lockdown" directory in the lib dir add two files: init.rb and session.rb.  Modify init.rb to set defaults and define the rules that apply to your system.
+This will create a "lockdown" directory in the lib dir add two files: init.rb and session.rb.
+Modify init.rb to set configuration options and define the permissions and user groups that apply to your system.
-<strong> Some noteworthy points:</strong>
+<strong> Please keep the following in mind:</strong>
 <ul>
 <li><strong>All Permissions are defined in init.rb, they cannot be defined via the administration screens.</strong></li>
-<li><strong>All User Groups should be defined in init.rb. The administration screens can be used to create user groups, but doing so should be reserved for the unexpected.</strong></li>
-<li><strong>Lockdown will sync up the rules (Permissions and User Groups) defined in init.rb with your database.</strong></li>
+<li><strong>All User Groups should be defined in init.rb. The administration screens can be used to create user groups, but doing so should be reserved for the unexpected. Creating User Groups via the administration screens will only add more work for you if you want to run tests using those groups.</strong></li>
+<li><strong>Lockdown will sync up the rules (Permissions and User Groups) defined in init.rb with your database.  You can turn off this feature.</strong></li>
 </ul>
-To help you with your new application, Lockdown comes with a generator called lockdown_all.
+To help you with your new application, Lockdown comes with a generator called lockdown that has various options for you to pick which templates you desire.
 <pre>
 $ cd <your_project_directory>
-$ ./script/generate lockdown_all
+$ ./script/generate lockdown --all
 </pre>
 This will install resources such as:
@@ -45,20 +43,11 @@ Please refer to the <a href="generator.html">generator page</a> for more detail.
 h2. How it works
-Lockdown stores an array of access rights in the session.  For example, if you have a standard REST users controller, the access rights would be:
+When Lockdown is installed, it adds the following line to your environment.rb (init.rb for Merb):
 <pre>
-  users/index
-  users/show
-  users/edit
-  users/update
-  users/new
-  users/create
-  users/destroy (delete for Merb)
+  require "lockdown/init"
 </pre>
-The above list will be stored in the session as an array and each request is tested against this list.
-To define access rights you need to modify lib/lockdown/init.rb.  This is the default init.rb included with Lockdown:
+This is the default init.rb included with Lockdown:
 <pre syntax="ruby">
 require "lockdown"
 require File.join(File.dirname(__FILE__), "session")
@@ -82,6 +71,10 @@ Lockdown::System.configure do
   # Set redirect to path on successful login:
   #       options[:successful_login_path] = "/"
   #
+  # Set the system to sync the Permissions and UserGroups defined here
+  # with the database.
+  #       options[:sync_init_rb_with_db] = true
+  #
   #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   # Define permissions
   #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -147,14 +140,41 @@ Lockdown::System.configure do
   # Define your user groups here:
 end
 </pre>
+As you can see, the first line requires lockdown.  This will load the Lockdown system which consists of various parts:
+<ul>
+  <li>
+    Controller<br/>
+    <p>The controller functionality will add before filters to test each request agains the defined access_rights for the current user.  If the current request is not in the access_rights list, access right is denied.</p>
+  </li>
+  <li>
+    Model<br/>
+    <p>The model functionality will automatically set the updated_by/created_by fields of your model to the current_profile_id.</p>
+  </li>
+  <li>
+    View<br/>
+    <p>The view functionality intercepts the link_to method (aliases it).  If the current user does not have rights to the link, the link will not show.<br/>There is also a link_to_or_show method (same params as link_to) that will print out just the name of the link (no anchor tag) if the current user does not have access. </p>
+  </li>
+</ul>
+When referring to access rights: if you have a standard REST users controller, the access rights would be:
+<pre>
+  users/index
+  users/show
+  users/edit
+  users/update
+  users/new
+  users/create
+  users/destroy (delete for Merb)
+</pre>
 h2. The internals
 All configuration of Lockdown (Permissions and User Groups) are done in lib/lockdown/init.rb.  The database functionality is merely an extension of the definitions to allow for the dynamic creation of User Groups.  Permissions can not be created via the administration screens.
-Lockdown doesn't have a concept of Roles. Instead, Lockdown users can be associated to one or many User Groups to allow for flexibility.  In addition, you can use the admin screens to add new User Groups to the database.
+Lockdown doesn't have a concept of Roles. Instead, Lockdown users can be associated to one or many User Groups to allow for flexibility.  In addition, you can use the admin screens to add new User Groups to the database. User groups are nothing more than a grouping mechanism for Permissions to ease management.
 Here are the parts to Lockdown:
@@ -198,7 +218,20 @@ Here are the parts to Lockdown:
   </li>
 </ul>
-h2. Forum
+h2. Roadmap to 1.0
+<strong>**this is tentative and the feature order may change</strong>
+<ul>
+  <li><strong>0.5.0: </strong>More generators to ease installation into existing projects</li>
+  <li><strong>0.6.0: </strong>Password reset/reminder, Registration page template generators</li>
+  <li><strong>0.7.0: </strong>OpenId support</li>
+  <li><strong>0.8.0: </strong>RSpec tests and helper methods for your application</li>
+  <li><strong>0.9.0: </strong>Merb Support</li>
+  <li><strong>1.0.0: </strong>Model level security</li>
+</ul>
+h2. Google Group
 If you are having a problem understanding how to use Lockdown, please post your question on the lockdown group.  If it's documentation related, I will keep this page updated to help everyone.
@@ -217,7 +250,10 @@ h2. License
 This code is free to use under the terms of the MIT license.
 h2. Contact
-Comments and suggestions are welcome via the "forum":http://groups.google.com/group/stonean_lockdown?hl=en
+Comments and suggestions are welcome via the "google group":http://groups.google.com/group/stonean_lockdown?hl=en
+<a href="http://blog.stonean.com">Andrew Stone</a>

data/website/model.jpg ADDED Viewed

Binary file

metadata CHANGED Viewed

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: lockdown
 version: !ruby/object:Gem::Version
-  version: 0.4.6
+  version: 0.5.0
 platform: ruby
 authors:
 - Andrew Stone
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
-date: 2008-05-08 00:00:00 -04:00
+date: 2008-05-22 00:00:00 -04:00
 default_executable:
 dependencies:
 - !ruby/object:Gem::Dependency
@@ -34,6 +34,7 @@ extra_rdoc_files:
 - Manifest.txt
 - PostInstall.txt
 - README.txt
+- website/generator.txt
 - website/index.txt
 files:
 - History.txt
@@ -59,6 +60,41 @@ files:
 - lib/lockdown/system.rb
 - lib/lockdown/version.rb
 - lib/lockdown/view.rb
+- rails_generators/lockdown/USAGE
+- rails_generators/lockdown/lockdown_generator.rb
+- rails_generators/lockdown/templates/app/controllers/permissions_controller.rb
+- rails_generators/lockdown/templates/app/controllers/sessions_controller.rb
+- rails_generators/lockdown/templates/app/controllers/user_groups_controller.rb
+- rails_generators/lockdown/templates/app/controllers/users_controller.rb
+- rails_generators/lockdown/templates/app/helpers/permissions_helper.rb
+- rails_generators/lockdown/templates/app/helpers/user_groups_helper.rb
+- rails_generators/lockdown/templates/app/helpers/users_helper.rb
+- rails_generators/lockdown/templates/app/models/permission.rb
+- rails_generators/lockdown/templates/app/models/profile.rb
+- rails_generators/lockdown/templates/app/models/user.rb
+- rails_generators/lockdown/templates/app/models/user_group.rb
+- rails_generators/lockdown/templates/app/views/permissions/_data.html.erb
+- rails_generators/lockdown/templates/app/views/permissions/index.html.erb
+- rails_generators/lockdown/templates/app/views/permissions/show.html.erb
+- rails_generators/lockdown/templates/app/views/sessions/new.html.erb
+- rails_generators/lockdown/templates/app/views/user_groups/_data.html.erb
+- rails_generators/lockdown/templates/app/views/user_groups/_form.html.erb
+- rails_generators/lockdown/templates/app/views/user_groups/edit.html.erb
+- rails_generators/lockdown/templates/app/views/user_groups/index.html.erb
+- rails_generators/lockdown/templates/app/views/user_groups/new.html.erb
+- rails_generators/lockdown/templates/app/views/user_groups/show.html.erb
+- rails_generators/lockdown/templates/app/views/users/_data.html.erb
+- rails_generators/lockdown/templates/app/views/users/_form.html.erb
+- rails_generators/lockdown/templates/app/views/users/_password.html.erb
+- rails_generators/lockdown/templates/app/views/users/edit.html.erb
+- rails_generators/lockdown/templates/app/views/users/index.html.erb
+- rails_generators/lockdown/templates/app/views/users/new.html.erb
+- rails_generators/lockdown/templates/app/views/users/show.html.erb
+- rails_generators/lockdown/templates/db/migrate/create_admin_user_and_user_group.rb
+- rails_generators/lockdown/templates/db/migrate/create_permissions.rb
+- rails_generators/lockdown/templates/db/migrate/create_profiles.rb
+- rails_generators/lockdown/templates/db/migrate/create_user_groups.rb
+- rails_generators/lockdown/templates/db/migrate/create_users.rb
 - rails_generators/lockdown_all/USAGE
 - rails_generators/lockdown_all/lockdown_all_generator.rb
 - rails_generators/lockdown_all/templates/app/controllers/permissions_controller.rb
@@ -108,8 +144,12 @@ files:
 - test/test_lockdown_all_generator.rb
 - test/test_lockdown_generator.rb
 - test/test_lockdown_models_generator.rb
+- website/generator.html
+- website/generator.txt
+- website/index.html
 - website/index.txt
 - website/javascripts/rounded_corners_lite.inc.js
+- website/model.jpg
 - website/stylesheets/screen.css
 - website/template.html.erb
 has_rdoc: true