Sha256: 364d343bedd5c0df99bff2547f9acf44be4f227c8a9c552832bb16a5086e4306
Contents?: true
Size: 1.08 KB
Versions: 55
Compression:
Stored size: 1.08 KB
Contents
# Namespacing in Bullet Train ## The `Account` Namespace for Controllers and Views Bullet Train comes preconfigured with an `Account` namespace for controllers and views. This is the place where Super Scaffolding will, by default, put new resource views and controllers. The intention here is to ensure that in systems that have both authenticated resource workflows and public-facing resources, those two different facets of the application are served by separate resource views and controllers. (By default, public-facing resources would be in the `Public` namespace.) ## Alternative Authenticated Namespaces In Bullet Train applications with [multiple team types](/docs/teams.md), you may find it helpful to introduce additional controller and view namespaces to represent and organize user interfaces and experiences for certain team types that vary substantially from the `Account` namespace default. In Super Scaffolding, you can specify a namespace other than `Account` with the `--namespace` option, for example: ``` rails generate super_scaffold Event Team name:text_field --namespace=customers ```
Version data entries
55 entries across 55 versions & 1 rubygems