A very simple in-memory filesystem is available which is only accessible via HTTP under /memfs. Use the POST or PUT method with the path to that file. The body of the request contains the contents of the file. No particular encoding or Content-Type is required. The file can then be downloaded from the same path.
This filesystem is practical for often changing data (e.g. HLS live stream) in order not to stress the disk or to wear out a flash drive. Also you don't need to setup a RAM drive or similar on your system.
The returned Content-Type is based solely on the file extension. For a list of known mime-types and their extensions see storage.mime_types in the configuration.
Access protection
It is strongly recommended to enable a username/password (HTTP Basic-Auth) protection for any PUT/POST and DELETE operations on /memfs. GET operations are not protected.
By default HTTP Basic-Auth is enabled with the username "admin" and a random password.
Fetch a file from the memory filesystem
get
Fetch a file from the memory filesystem
Path parameters
pathstringRequired
Path to file
Responses
200
OK
Responsestring
301
Moved Permanently
404
Not Found
get
/memfs/{path}
Add a file to the memory filesystem
put
Writes or overwrites a file on the memory filesystem
Authorizations
AuthorizationstringRequired
Path parameters
pathstringRequired
Path to file
Bodyinteger[]
integer[]Optional
Responses
201
Created
204
No Content
507
Insufficient Storage
put
/memfs/{path}
Remove a file from the memory filesystem
delete
Remove a file from the memory filesystem
Authorizations
AuthorizationstringRequired
Path parameters
pathstringRequired
Path to file
Responses
200
OK
text/plain
Responsestring
404
Not Found
text/plain
delete
/memfs/{path}
Example:
Use these endpoints to, e.g., store HLS chunks and .m3u8 files (in contrast to an actual disk or a ramdisk):
Then you can play it generally with, e.g.,
ffplay http://127.0.0.1:8080/memfs/foobar.m3u8.
API
The contents of the /memfs are also accessible via the API in the same way as described above, but with the same protection as the API (see API-Security configuration) for all operations. It is also possible to list all files that are currently in the filesystem.
Create, Update
Example:
The contents for the upload has to be provided as an io.Reader.
After the successful upload the file is available at /memfs/example.txt and /api/v3/fs/mem/example.txt.
Description:
Add a file to the memory filesystem
put
Writes or overwrites a file on the memory filesystem
Authorizations
AuthorizationstringRequired
Path parameters
pathstringRequired
Path to file
Bodyinteger[]
integer[]Optional
Responses
201
Created
204
No Content
507
Insufficient Storage
put
/api/v3/fs/mem/{path}
Read
List all files
Listing all currently stored files is done by calling /api/v3/fs/mem. It also accepts the query parameters pattern, sort (name,size, or lastmod) and order (asc or desc). If none of the parameters are given, all files will be listed sorted by their last modification time in ascending order.
With the pattern parameter you can filter the list based on a glob pattern, with the addition of the ** placeholder to include multiple subdirectories, e.g. listing all .ts file in the root directory has the pattern /*.ts, listing all .ts file in the whole filesystem has the pattern /**.ts.
Example:
Description:
List all files on the memory filesystem
get
List all files on the memory filesystem. The listing can be ordered by name, size, or date of last modification in ascending or descending order.
Authorizations
AuthorizationstringRequired
Query parameters
globstringOptional
glob pattern for file names
sortstringOptional
none, name, size, lastmod
orderstringOptional
asc, desc
Responses
200
OK
application/json
get
/api/v3/fs/mem
200
OK
Download a file
For downloading a file you have to specify the complete path and filename. The Content-Type will always be application/data.
Example:
The returned data is an io.ReadCloser.
Description:
Fetch a file from the memory filesystem
get
Fetch a file from the memory filesystem
Authorizations
AuthorizationstringRequired
Path parameters
pathstringRequired
Path to file
Responses
200
OK
Responsestring
301
Moved Permanently
404
Not Found
get
/api/v3/fs/mem/{path}
Link
Linking a file will return a redirect to the linked file. The target of the redirect has to be in the body of the request.
Example:
This is not implemented in the client.
Description:
Create a link to a file in the memory filesystem
patch
Create a link to a file in the memory filesystem. The file linked to has to exist.
Authorizations
AuthorizationstringRequired
Path parameters
pathstringRequired
Path to file
Body
stringOptional
Responses
201
Created
400
Bad Request
patch
/api/v3/fs/mem/{path}
Delete
For deleting a file you have to specify the complete path and filename.