It's possible to setup authentication for readers too:
It's possible to setup authentication for readers too:
```yml
```yml
paths:
pathDefaults:
all:
readUser: user
publishUser: myuser
readPass: userpass
publishPass: mypass
readUser: user
readPass: userpass
```
```
If storing plain credentials in the configuration file is a security problem, username and passwords can be stored as sha256-hashed strings; a string must be hashed with sha256 and encoded with base64:
If storing plain credentials in the configuration file is a security problem, username and passwords can be stored as sha256-hashed strings; a string must be hashed with sha256 and encoded with base64:
All available recording parameters are listed in the [sample configuration file](/mediamtx.yml).
All available recording parameters are listed in the [sample configuration file](/mediamtx.yml).
Be aware that not all tracks can be saved. A compatibility matrix is available at the beginning of the README.
Be aware that not all codecs can be saved with all formats, as described in the compatibility matrix at the beginning of the README.
To upload recordings to a remote location, you can use _MediaMTX_ together with [rclone](https://github.com/rclone/rclone), a command line tool that provides file synchronization capabilities with a huge variety of services (including S3, FTP, SMB, Google Drive):
To upload recordings to a remote location, you can use _MediaMTX_ together with [rclone](https://github.com/rclone/rclone), a command line tool that provides file synchronization capabilities with a huge variety of services (including S3, FTP, SMB, Google Drive):
@ -1172,17 +1167,14 @@ To upload recordings to a remote location, you can use _MediaMTX_ together with
3. Place `rclone` into the `runOnInit` and `runOnRecordSegmentComplete` hooks:
3. Place `rclone` into the `runOnInit` and `runOnRecordSegmentComplete` hooks:
```yml
```yml
record: yes
pathDefaults:
# this is needed to sync segments after a crash.
paths:
# replace myconfig with the name of the rclone config.