====== Develop a standardized directory hierarchy ======


===== Overview =====

**Launchpad URL:** [[https://blueprints.launchpad.net/sapidlib/+spec/logical-directory-layout|https://blueprints.launchpad.net/sapidlib/+spec/logical-directory-layout]]

**Description:** Develop a standardized directory hierarchy that will set the stage for our future "package" model and that takes into account that permissions for objects are based off file location. The hierarchy should be clean, logical, and versatile.

**Components affected:** Entire mudlib

**Contributors:** CodySomerville

===== Release Notes =====

//Describe what should be in the release notes when this is implemented//

===== Rationale =====

//Describe the rationale of this specification//

===== Use Cases =====

//Describe two or more use cases//

===== Design =====

//Describe the design of this specification//

===== Implementation =====

//Describe how this specification will be implemented//


===== Discussion =====

== Secure directories for different user levels ==

A directory structure needs to be sorted out, so that sensitive data for each of the priv levels can be put and yet only the authorized user will be able to see the data, ie,

  * A directory for admin logs and data.
  * A directory for developer logs and data.
  * A directory for user logs and data.


With the proper access rights, admin can see all obviously, developer will see all but not admin and user will only be able to access the user directory.

 --- //[[harrison.rt@gmail.com|Richard Harrison]] 2008/01/21 23:01//