Generators – subsite

Usage

rails generate hobo:subsite NAME [options]

Options

    [--skip-namespace]                         # Skip namespace (affects only isolated applications)
    [--user-resource-name=USER_RESOURCE_NAME]  # User Resource Name
                                               # Default: user
    [--old-style-hash]                         # Force using old style hash (:foo => 'bar') on Ruby >= 1.9
    [--ui-theme=UI_THEME]                      # jQuery-UI Theme
                                               # Default: flick
    [--theme=THEME]                            # Theme
                                               # Default: clean_admin
-t, [--test-framework=NAME]                    # Test framework to be invoked
                                               # Default: test_unit
-i, [--invite-only]                            # Add features for an invite only website

Runtime options

-q, [--quiet]    # Suppress status output
-s, [--skip]     # Skip files that already exist
-f, [--force]    # Overwrite files that already exist
-p, [--pretend]  # Run but do not make any changes

Description

  Creates a subsite, a namespaced section of your application.

  Controllers for the subsite are created in
  app/controllers/<subsite_name>/ and views are also in their own
  subdirectory.   This allows you to have two different controllers
  and two different sets of views for the same model.

  The subsite will use app/views/taglibs/<subsite_name>_site.dryml
  for common tags. The assets that the subsite will load are
  specified in app/assets/javascripts/<subsite_name>.js and
  app/assets/stylesheets/<subsite_name>.[s]css

  The difference between hobo:admin_site and hobo:subsite is that
  hobo:admin_site limits the subsite to use by administrators only.

Edit this page