154673f3d8
* docs: changes based on DX changes * remove fields no longer needed * remove unnecessary parameters * fixes to authenticate middleware usage * add highlight to migrations config * change configuration to http * added missing remote link docs * fix name in sidebar * added notification module docs + updated file module docs * add vale exceptions * fix vale errors * added docs on custom cli scripts
28 lines
877 B
Plaintext
28 lines
877 B
Plaintext
import { ChildDocs } from "docs-ui"
|
||
|
||
export const metadata = {
|
||
title: `File Provider Modules`,
|
||
}
|
||
|
||
# {metadata.title}
|
||
|
||
A File Module exposes the functionalities to upload assets, such as product images, to the Medusa application.
|
||
|
||
---
|
||
|
||
## What is a File Provider Module?
|
||
|
||
A file provider module implements the logic of handling uploads and downloads. The File Module must have one file provider module configured.
|
||
|
||
By default, Medusa uses the Local File Module. This module uploads files to the `uploads` directory of your Medusa application.
|
||
|
||
This is useful for development. However, for production, it’s highly recommended to use other File Modules, such as the S3 Module.
|
||
|
||
<ChildDocs type="item" filters={["Guides"]} onlyTopLevel={true} />
|
||
|
||
---
|
||
|
||
## Create a File Provider Module
|
||
|
||
To create a file provider module, refer to [this guide](/references/file-provider-module).
|