# Local Provider Use the local provider to store files in a local filesystem where your application is running. Behind the scenes it leverages the Java `nio` package to provide concurrency, atomicity, and non-blocking operations. ## Configuration ### Example

moduleSettings = {
  "cbfs": {
	// The default disk with a reserved name of 'default'
	"defaultDisk" : "myStorage",
	// Register the disks on the system
	"disks"       : {
	  // Your default application storage
	  "myStorage" : {
		"provider"   : "Local",
		"properties" : { 
			"path" : "#controller.getAppRootPath()#.myStorage",
			"diskUrl" : function(){
				return variables.controller
					.getRequestService()
					.getContext()
					.getHtmlBaseUrl()
					& "storage/.mystorage/";
			}
		}
	  }
	}
  }
};

### Properties When configuring your local disks, the following properties are available:

Property	Type	Default	Description
`autoExpand`	`Boolean`	false	If true, it will use an `expandPath()` on the path property. Else it leaves it as is.
`diskUrl`	`http(s)`	`null`	The public disk Url. This is used to create file URLs and temporary URLs. This should point to the root path but in a web-accessible format.
`path`	`string`	--	The relative or absolute path of where to store the file system.
`uploadMimeAccept`	`string`	*	The mime types which are accepted via the upload method. Defaults to all.
`visibility`	`string`	`public`	The default visibility when creating files. Available options are `public, private, readonly`

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cbfs.ortusbooks.com/getting-started/providers/local-provider.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.