7b64fc7c30
* Create http auth middleware * Add support for ending the inbound stream. Closes #191 * Add a simple success response to API requests |
||
|---|---|---|
| .github | ||
| .vscode | ||
| config | ||
| controllers | ||
| core | ||
| doc@54a0ee1396 | ||
| metrics | ||
| models | ||
| router | ||
| scripts | ||
| static | ||
| test | ||
| utils | ||
| webroot | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmodules | ||
| CODE_OF_CONDUCT.md | ||
| config-example.yaml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| README.md | ||
Take control over your content and stream it yourself.
Explore the docs »
View Demo
·
FAQ
.
Report Bug
Table of Contents
- About the Project
- Getting Started
- Use with your broadcasting software
- Video storage and distribution options
- Building from source
- License
- Contact
About The Project
In 2020 the world changed when everyone become stuck in their homes, looking for creative outlets to share their art, skills and themselves from inside their bedroom.
This created an explosion of live streaming on Facebook Live, YouTube Live, Instagram, and Twitch. These services provided everything they needed, an easy way to live stream to the world, and a chat for users to be a part of their community.
But in a world where many were previously finding ways to rely on the big internet service companies less, the 2020 COVID-19 pandemic made everyone run right back to them.
And as soon as people started streaming their DJ sets, movie watching parties, and themselves just sitting around listening to music the big companies came to mute their streams, remove their recordings or ban these users all together.
That's when I wanted a better option for people. Something you could run yourself and get all the functionality of these services, where you could live stream to an audience and and allow them to take part in the chat, just like they've been used to on all the other services. But instead of handing control over to somebody else, you run it. You won't get shut down, and you own it all, just like it should be.
I figured you can install Wordpress and self-host your blog, or install Megento and self-host your e-commerce site. You can install Icecast and have your own internet radio station. Spin up an instance of Mastodon and you have your own social media site that you control. You can even install Nextcloud and have your own personal productivity service replacing Dropbox and Google Docs. There's an open-source alternative to all the big services that you can run for almost everything, but I couldn't think of what the live video streaming equivalent was. There should be a independent, standalone Twitch in a Box.
Keep in mind that while streaming to the big social companies is always free, you pay for it with your identity and your data, as well as the identity and data of every person that tunes in. When you self-host anything you'll have to pay with your money instead. But running a self-hosted live stream server can be done for as cheap as $5/mo, and that's a much better deal than selling your soul to Facebook, Google or Amazon.
Getting Started
The goal is to have a single service that you can run and it works out of the box. Visit the Quickstart to get up and running.
Configuration
Many aspects can be adjusted and customized to your preferences. Read more about Configuration to update the web UI, video settings, and more.
Web interface + chat
Owncast includes a web interface to your video with built-in chat that is available once you start the server.
The web interface was specifically built to be editable by anybody comfortable tweaking a web page. It's not bundled or transpiled into anything, it's just HTML + Javascript + CSS that you can start editing.
Read more about the features provided and how to configure them in the web documentation.
Use with your existing broadcasting software
In general Owncast is compatible with any software that uses RTMP to broadcast to a remote server. RTMP is what all the major live streaming services use, so if you’re currently using one of those it’s likely that you can point your existing software at your Owncast instance instead.
OBS, Streamlabs, Restream and many others have been used with Owncast. Read more about compatibility with existing software.
Video storage options
Two ways of storing and distributing the video are supported.
- Locally via the built-in web server.
- S3-compatible storage.
Local file distribution
This is the simplest and works out of the box. In this scenario video will be served to the public from the computer that is running the server. If you have a fast internet connection, enough bandwidth alotted to you, and a small audience this may be fine for many people.
S3-Compatible Storage
Instead of serving video directly from your personal server you can use a S3 compatible storage provider to offload the bandwidth and storage requirements elsewhere.
Read more detailed documentation about configuration of S3-compatible services.
Building from Source
- Ensure you have the gcc compiler configured.
- Install the Go toolchain.
- Clone the repo.
git clone https://github.com/owncast/owncast - Follow the above Getting Started instructions, making sure ffmpeg exists and your config file is set.
go run main.goon the first run will download the required packages needed for the application to build.- It will start running the same as in the above Usage instructions and you can point OBS to your localhost instance of it.
There is also a supplied Dockerfile so you can spin it up from source with little effort. Read more about running from source.
License
Distributed under the MIT License. See LICENSE for more information.
Contact
Gabe Kangas - @gabek@mastodon.social - email gabek@real-ity.com
Project Link: https://github.com/owncast/owncast