You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pulling from the web archive as the current Pixelfed doc site seems to have no documentation, these three features are listed as "optional features" in the docs due to requiring additional setup steps and manual configuration in the Pixelfed env and nginx conf.
However, the setup for these is pretty involved and is not super tightly integrated into Pixelfed proper. It very much feels like an experimental feature that's not fully put together yet. I'd love to see these features become things you can configure in the Pixelfed settings and, ideally, have the ability to use it with an external rtmp server instead of being specifically tied to nginx-rtmp as I use traefik for my pixelfed setup. Also, self-hosted solutions for chat outside of pusher may also be a good move too, possibly prosody.
The text was updated successfully, but these errors were encountered:
Pulling from the web archive as the current Pixelfed doc site seems to have no documentation, these three features are listed as "optional features" in the docs due to requiring additional setup steps and manual configuration in the Pixelfed env and nginx conf.
http://web.archive.org/web/20240105020534/https://docs.pixelfed.org/running-pixelfed/optional-features/livestreaming/
However, the setup for these is pretty involved and is not super tightly integrated into Pixelfed proper. It very much feels like an experimental feature that's not fully put together yet. I'd love to see these features become things you can configure in the Pixelfed settings and, ideally, have the ability to use it with an external rtmp server instead of being specifically tied to nginx-rtmp as I use traefik for my pixelfed setup. Also, self-hosted solutions for chat outside of pusher may also be a good move too, possibly prosody.
The text was updated successfully, but these errors were encountered: