GitHub/matterbridge
3
0
Fork 0
mirror of https://github.com/42wim/matterbridge.git synced 2025-04-21 23:27:52 +02:00
Code Issues Projects Releases Wiki Activity

Update mediaserver information

Wim 2018-07-21 17:48:47 +02:00
parent c987a2ae0e
commit ec251797ca
1 changed files with 33 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
Mediaserver-setup-[advanced].md

@ -1,11 +1,21 @@
# Caddy
Matterbridge is not going to implement it's own "mediaserver" instead we make use of other tools that are good at this sort of stuff. In this case we're using caddy for upload/downloading media.
Caddy has automatic https support, so I'm going to describe this for https only.
Matterbridge is not going to implement it's own "mediaserver" instead we make use of other tools that are good at this sort of stuff.
This mediaserver will be used to upload media to services that don't have support for uploading images/video/files.
At this moment this is xmpp, gitter and irc
## caddy install / configuration
There are 2 options to set this up:
* You already have a webserver running
* Matterbridge runs on the same server see [local download](#use-local-download)
* Matterbridge runs on another server. If the webserver is using caddy, see [caddy](#use-remote-upload)
* You don't have a webserver running
* See [caddy](#use-remote-upload)
# Use remote upload
## Caddy
In this case we're using caddy for upload/downloading media.
Caddy has automatic https support, so I'm going to describe this for https only.
### caddy install / configuration
Go to https://caddyserver.com/download
Enable `http.upload` as plugin
@ -23,7 +33,7 @@ yourserver.com:443 {
}
}
```
## matterbridge configuration
### matterbridge configuration
configuration needs to happen in `[general]`
```
[general]
@ -31,3 +41,20 @@ MediaServerUpload="https://a_user:a_password@yourserver.com/upload"
MediaServerDownload="https://yourserver.com/"
```
# Use local download
In this case we're using matterbridge to download to a local path your webserver has read access to and matterbridge has write access to.
Matterbridge is running on this same server.
## matterbridge configuration
In this example the local path matterbridge has write access to is `/var/www/matterbridge`
Your server (apache, nginx, ...) exposes this on `http://yourserver.com/matterbridge` (nginx, apache configuration is out of scope)
configuration needs to happen in `[general]`
```
[general]
MediaDownloadPath="/var/www/matterbridge"
MediaServerDownload="https://yourserver.com/matterbridge"
```